Hi!
> > The latest jBoss release (see jboss.org for download) contains embedded
> > Tomcat 3.2 integration and support for "java:comp/env" namespace where
> > you can bind environment entries, resource references, and EJB
> > references.
>
> All I can say is that I hate licenses.... ( GPL, Apache - all of them ).
Me too. So? What does this have to do with JNDI?
> > On an implementation note, we solved the "java:comp/" namespace by
> > switching context based on thread contextclassloader. Because of this we
> > do not need anything special other than the AdaptiveClassLoader being
> > set properly on servlet request. Note that "java:/" is *NOT* context
> > switched but global to the entire JVM. This is where we bind the
> > transaction manager, connection pools, etc.
>
> There are few issues with accessing/using the ClassLoader to do that, but
> it should work in most cases.
>
> ( the problems are related with sandboxing and exposing only a minimal set
> of informations, AdaptiveClassLoader can also be replaced by
> URLClassLoader in JDK1.2, etc)
Not sure what you mean. Each application has its own ACL right? Or what
would be the problem? Can you expand on this point.
regards,
Rickard
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
