On Jan 17, 2006, at 2:19 PM, David Jencks wrote:
On Jan 17, 2006, at 1:48 PM, Dain Sundstrom wrote:
The jndi-name is supposed to be the name to which the Home
interface is bound and the local-jndi-name is the name to which
the LocalHome interface is bound. An application should be able
to look up a home using the name at any time. Of course remote
clients can not lookup the LocalHome, but both should be available
in global JNDI for applications in the same Java VM.
I would have -1ed the removal of the global JNDI namespace if I
had realized that it was removed, and I feel strongly that we
should put it back in ASAP.
There may be 2 or more "global jndi namespaces". There was one I
implemented, based on an old version of read-only context, and for
a while connectors were able to be bound there. I removed this
binding, and no one objected at the time. EJBs have never been
bound into this AFAIK. I think perhaps we should finish removing
this one.
I think we should remove all of the half implemented ones, so we only
have the very simple read-only one left. At that point, I hope
someone would add a very very simple global mutable JNDI
implementation. I think openejb 1 has some code that can be used as
the basis for the new global mutable JNDI impl.
There is also, I think, some openejb-specific jndi context, and
possibly the jndi-name and local-jndi-name are related to binding
into this one. I have no idea what the status of this is.
I don't think there is one, but there maybe one in the openejb1 tree.
I don't particularly like there being so many unrelated jndi
implementations, and would like them all to be in one place with
clearly defined capabilities and uses.
I agree.
-dain
