Ok, thanks for the clarification. The real issue is that the EJBs needed
to specify their resource-refs via jboss.xml entries.
----- Original Message -----
From: "Rickard Öberg" <[EMAIL PROTECTED]>
To: "JBoss-Dev" <[EMAIL PROTECTED]>
Sent: Tuesday, February 20, 2001 4:41 AM
Subject: Re: [jBoss-Dev] latest tomcat-service.jar broke JNDI namespace
Hi!
Scott M Stark wrote:
> The final problem with the latest tomcat-service and the petstore app is
> an issue with how the resource refs from the jboss-web.xml file are mapped
> into the jboss server JNDI namespace. The problem that JbossWebXmlReader
> is performing this mapping from the thread in which the web app is deployed
> and it is binding into the java:comp/env context which is a thread local namespace.
> When the servlet requests run they are using a different thread and so the
> namespace is incorrect.
That is an incorrect understanding of it: "comp/env" is *classloader*
local. Threads are used locally, but the bindings relate to the
classloader that is set as thread contextclassloader.
As long as the right CL is associated with a thread there is no problem.
/Rickard
--
Rickard Öberg
Email: [EMAIL PROTECTED]
