Posted by eudesf
on March 25, 2010 at 4:36 AM PDT
I've been in trouble with Glassfish v3 JNDI naming last days... Then I have made some tests and realize that:
When we use a bean with two interfaces or a no-interface bean inside an EAR, Glassfish uses JNDI names prefixed by EAR name as defined in the EJB 3.1 specification. It is great!
But when we deploy a bean (also in an EAR) with only one remote interface, the Glassfish publishes Glassfish-specific names (full qualified name of the remote interface), as used in versions earlier than v3.
Is this OK?
If yes, why the Glassfish-specific (non-portable) names are used in this case? There is any way to avoid this, without making changes in sun-ejb-jar.xml for each bean?