On Jan 16, 2006, at 10:53 AM, Aaron Mulder wrote:
All (and David Blevins in particular),
Currently we let you set both a jndi-name and local-jndi-name on an
EJB (and I assume each only works if the EJB has the corresponding
interface).
It's pretty clear that the jndi-name can be used by an application
client that wants to look up and invoke the EJB via its remote/home
interfaces.
I don't see how the local-jndi-name can be used. Since we removed the
"global JNDI space" on the server side, I think all JNDI access is
effectively remote, and therefore you couldn't talk to the EJB through
its local/local home interfaces. Is that right? Should the
local-jndi-name element be deprecated and/or removed?
Been working on code to try and add embedded testing in and you need
at least a small, ejb-only, global-jndi for that. I may not be able
to work it in, but I'd say leave it in for now and clearly document
it as not being used in Geronimo.
-David
