Hey
Scott Seligman wrote:
> > > in JNDI 1.2, it is possible
> > > for different containers within a single VM to provide different
> > > implementations of the "java:" namespace. (This was not the case in
> > > JNDI 1.1.x.) This would be implemented by each container having its
> > > own JNDI application resource file specifying the URL context factory
> > > for its "java:" namespace.
> >
> > Hm.. you say this will work, but I have decompiled the NamingManager...
>
> JNDI application resource files are described here:
>
>
>http://java.sun.com/products/jndi/1.2/javadoc/javax/naming/InitialContext.html#ENVIRONMENT
Sure, this would work, but I'd still suggest that you fix the
NamingManager as suggested. It is still a bug since it doesn't allow
ObjectFactories to return null.
> Note that two initial contexts may not have the same value for any
> given environment property. In particular, two initial contexts
> within two different beans (or other application components) may
> have different values for the property listing the URL context factory
> locations.
By making a custom classloader for each component which contains
component specific jndi.properties, right?
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
Homepage: http://www-und.ida.liu.se/~ricob684
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
