glassfish_at_javadesktop.org wrote:
> By default, a Remote EJB's global JNDI name defaults to the fully qualified class name of
> its business interface. This is a ease-of-use feature which handles the bulk of the simple
> cases. However, in your case if you have multiple EJBs that expose the same Remote
> business interface, either in the same application or different applications, you need to
> explicitly select global JNDI names that are unique across the entire application server.
>
>
I wonder why GlassFish does not use the application and module name in
the default JNDI name of an EJB. That would have made the names more unique.
Thanks,
Sahoo