> You are not necessarily wrong in your interpretation of the EJB spec, but
> you might be in your interpretation of the JNDI spec.
>
> Whenever a JNDI name is prefixed with a string followed by a colon, as in
> "java:," the JNDI manager then tries to find a special naming context
> factory associated with that name. The JNDI specification does NOT allow
> for names of this type to not be "interpreted in any way." It should and
> does matter that the name looks like a JNDI URL...it IS a JNDI URL!!! The
> jBoss naming server IS a JNDI provider, and is constrained by the way JNDI
> works.
Correct.
> Even when looking up an ejb from outside the EJB container, you are still
> using JNDI. And the J2EE spec does not require "application clients" as
> they are called, to have any access to the "java:" namespace from JNDI.
Actually the latest version of the J2EE spec does have a notion of
"standalone application clients" which are allowed to use the java:
namespace. Eventually we will of course support this, but for now we go by
the old spec where standalone application clients must use the proprietary
naming conventions (i.e. lookup from InitialContext directly).
> I hope this clears things up. From looking at your email below, it looks
as
> if you think that external clients are NOT using JNDI to look up beans,
when
> they are. And the J2EE spec dictates that the "java:" namespace only
needs
> to be valid from within the server itself.
See above ;-) (I know, its difficult to keep up with all the new specs...)
> Again, some servers may do this anyway, like WebLogic. However,
understand
> that this is something they provide ON TOP of the spec. Coding clients
that
> assume that these services are present makes them non-portable.
See above :-)
We will get there too...
/Rickard
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
