----- Original Message -----
From: "Julian Gosnell" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, October 02, 2001 3:13 PM
Subject: Re: [JBoss-dev] problem with 2.4.1/jetty & jboss-website


> Scott,
>
> AFAIK (and in this area it's not much):
>
> ENC=Enterprise Naming Context.
>
> This is implemented via JNDI.
>
Right

> Jetty does not contain any JNDI related code - since this stuff only
becomes
> relevant within e.g. JBoss. Thus it is all left to the integration code.
>
> The integration code does not contain any JNDI stuff. This is all left to
my
> superclass - AbstractWebContainer.
>
The integration code must call the parseWebAppDescriptors with the
class loader that will be set as the thread context class loader by the web
container during any servlet calls. This is done by the
org.jboss.jetty.SetupHandler
class in the contrib/jetty on the 2.4 branch.

> JBoss-2.4.0/Jetty-3.1.RC8 works.
>
> JBoss-2.4.1/Jetty-3.1.RC9 and JBoss-2.4.1/Jetty-3.1.1 display the problem.
>
> I have built JBoss-2.4.0/Jetty-3.1.RC9 and 3.1.1 distributions which both
DO
> NOT display the problem.
>
> I have built a 2.4.2 release which does.display the problem.
>
> On the subject of the ClassLoader used for the webapp by Jetty. I have run
some
> tests and this is ALWAYS the actual ClassLoader passed to it by the or a
> descendent of this.
>
>
> So as far as I understand (unless I am mistaken about what the ENC is):
>
> 1. Jetty does not and has never created the war ENC, but expects
> AbstractWebContainer to do so.
> 2. Some change seems to have occurred between 2.4.0 and 2.4.1 which has
> possibly exacerbated a shortfall in the Jetty integration.
> 3. The stacktrace shows that AbstratWebContainer is trying to bind a
resource
> that has already been bound - possibly by it.
>
Does this happen for the jbosstest-web.ear or does there have to be multiple
wars in the ear for the problem to occur?

> I would really like to put this to bed sso and get a 2.4.2 release out.
>
> Any help that you can give me on this would be much appreciated,
>
>
> Why particularly do you implicate ClassLoaders? Would class name spaces
have
> any relevance to JNDI namespaces ? could you explain.
>
The uniqueness of any J2EE component ENC is based solely on the thread
context
class loader that first attempts to locate the java:comp context. ENCs are
indexed by
class loader in the ObjectFactory that is bound under the java:comp JNDI
context.
There was a change in 2.4.1 to help simplify the management of this
namespace so that
if a thread used a class loader that was a child of the class loader in
which an
java:comp context had been created, it would see the same context. Maybe
this
is causing a problem due to how the Jetty class loader operates.

Let me know if the jbosstest-web.ear causes the same problem and I'll look
into what
is occurring. If this doesn't cause the problem I'll try the jboss-website
ear. Is the
contrib/jetty code on the 2.4 branch up in synch with what I should be
looking at
for the Jetty-3.1.1 release?



_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to