All geek questions in one place

The meaning of all JNDI names in JBoss 7

I am deploying a Java EE application on JBoss 7.1.1, and when my beans session is deployed, JBoss displays a message stating that it has created several JNDI bindings. Something like that:

java:global/ear-name/jar-name/MyClassImpl!fully.qualified.path.to.Interface java:app/jar-name/MyClassImpl!fully.qualified.path.to.Interface java:module/MyClassImpl!fully.qualified.path.to.Interface java:jboss/exported/ear-name/jar-name/MyClassImpl!fully.qualified.path.to.Interface java:global/ear-name/jar-name/MyClassImpl java:app/jar-name/MyClassImpl java:module/MyClassImpl

It is slightly different from EJB to EJB, but that is a general idea.

I am confused by what is happening here. Why are there so many of them? Is there any difference between these JNDI bindings? If so, when should each be used?

+6
source share
1 answer

Here you can find all the documentation [1], but in brief some of them are dictated by the specification, and some by JBoss-specific functionality (mainly java: jboss / exported, java: jboss entries)

[1] https://docs.jboss.org/author/display/AS71/JNDI+Reference

+7
source

Source: https://habr.com/ru/post/915537/

More articles:


All Articles