We don't look into the war at all. Its now an atomic component.
It was looking into the war and finding jars that caused the
problems in the first place. If you want to deploy sars or
common jars you have to use an ear.

Its fine that Jetty can completely delegate all class loading, but Tomcat
won't allow this. It will delegate to a parent class loader but it will
continue to create its own class loaders as it sees fit for the war
contents. And if it first looks to its local WEB-INF/classes and
WEB-INF/lib before calling our class loaders, and then interacts
with an EJB that does see some shared classes in a WEB-INF/lib/jar
we found, I think we will again have class loader conflicts.

----- Original Message -----
From: "marc fleury" <[EMAIL PROTECTED]>
To: "Scott M Stark" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Thursday, February 21, 2002 4:14 AM
Subject: RE: [JBoss-dev] Why add anything from a war to the JBoss classpath


> <so-fucking-jet-lagged>
>
> Ok, I understand.  I think this is a safe call for now as we really need
> that DR1 to be public.   I will look into the issue closely with Jan from
> Jetty as I believe they are keen on dumping class loading madness on our
> lap.
>
> Class loading is one of the toughest problems in Java, one of the best
> features too...
>
> The only thing is that when you say "don't deploy any subcomponents of
war"
> do you mean that you don't even look for jars/sars or that you don't look
> for web-inf/classes stuff?
>
> marcf
>
> PS: and yes class.forName really is a pain in the ass :)
>



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

Reply via email to