Re: [jBoss-Dev] RE: [jBoss-User] JNDI Problem (and EmbeddedTomcat)

[Rickard �berg]

Hey

Kevin Lewis wrote:
> It was just convenient to be able to create my own Naming implementation
> and associate it with the current thread.
> 
> The problem now is that I don't know that I can create my context from a
> Tomcat thread/classloader (which is what invokes my context
> interceptor), even if I create a new BeanClassLoader and associate it
> with the current thread.  Where does the context go when the container
> creates the context for a bean?  How does the container "save off" the
> environment it creates during init?  This used to be in the
> BeanClassLoader.

As I said, the "comp" context takes care of the switching logic. All you
need to make sure is that the right context classloader is set. And in
case of Tomcat I think this is handled by default (i.e. Tomcat sets the
context classloader properly on both init and all requests). So, all you
should have to do is do the binding into java:comp/env at startup. The
rest is automatic. There's no need for a request-interceptor.

/Rickard

-- 
Rickard �berg

Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com