Does a java:app JNDI name used from within an .ear file require a moduleName component? -
i have ejb packaged in .ear
file.
this ejb needs reference ejb packaged in different .jar
file in same .ear
file.
the calling ejb not know module target ejb lives in.
from reading java ee specification, seems java:app
namespace for. think i'm allowed this:
final frobnicator f = (frobnicator)context.lookup("java:app/frobnicatorbean");
...but in glassfish 3.1.2.2 bean name not found.
i can see bean deployed , gets global jndi name assigned fine, exists, , bean name (frobnicatorbean
) above correct.
am misreading specification? must specify module name well? if so, java:app
namespace?
must specify module name well? if so, java:app namespace?
according ejb 3.1 specification :
4.4 global jndi access ->4.4.1.1 java:app
the java:app prefix allows component executing within java ee application access application-specific namespace.
the resulting syntax :
java:app/<module-name>/<bean-name>[!<fully-qualified-interface-name>]</html> note <module-name> required part of syntax...
Comments
Post a Comment