On Oct 1, 2006, at 8:16 PM, David Jencks wrote:
For connectors it's pretty easy, we can just have a repeating element
<global-jndi-name>foo</global-jndi-name>
For ejbs with the current 3 naming systems it's a bit harder. One
possibility would look something like this:
<jndi>
<global/>
<corba>
<tss-link>foo-tss</tss-link>
</corba>
<openejb/>
<remote-name>foo</remote-name>
<local-name>bar</local-name>
</jndi>
where the global, corba, and openejb elements indicate which naming
system to bind to and the names are supplied with remote-name and
local-name. A remote jndi would ignore the local-name elements.
You could have multiple jndi elements to get different bindings in
different naming systems.
What if the user specifies a single name that would bind into all
naming systems by default (as appropriate). If the user chooses to
be more specific or isolated in the bindings they could through some
extended XML. So one could use something like:
Bean w/remote and local interfaces.
<jndi>
<name>foo</name>
</jndi>
This would result in the same name being bound into the corba, remote
and local naming. I'd make global the default context although that
could be argued.
Perhaps one could simply bind the EJBName into all three contexts and
not have to specify this property at all.
Not knowing too much about the naming stuff I may be off the mark a
bit. But I'd make the defaults for no XML the most common so we
improve simplicity.
Matt Hogstrom
[EMAIL PROTECTED]
