Gabor -- the code looks right to me.
see my emails on 2/14/01 regarding the changes to tomcat service.
In short, what I think what is wrong is that Dewayne fixed tomcat service so
that it uses tomcat's server.xml. however he removed the code that adds the
app classloader to tomcat (via ContextClassLoaderInterceptor). Now it seems
that it is necessary to manually add this interceptor manually to the
server.xml file in order to cause it to be used. I have not gotten a
response from dewayne on this (I am cc ing him)
dewayne, if Im wrong I apologize for bugging you.
-----Original Message-----
From: Gabor Herr
To: JBoss-Dev
Sent: 2/16/01 9:03 AM
Subject: Re: [jBoss-Dev] bug in ear deployment in pre 2.1
-J2eeDeployer.java/Installer.java
Scott M Stark writes:
> I have applied these changes.
Thanks for the quick response.
Now it works for EJB-JARs but unfortunately not for WARs. I have two
WAR-modules in an EAR both referring to the same class in a library
JAR, which is set in both modules' Manifest-Classpath, but the class
is not found by Tomcat. Probably this is a problem related to Tomcat,
which perhaps has been already fixed in 4.0. Is there a working setup
for Tomcat-4.0 and JBoss?
Has anybody successfully used Manifest-Classpath in WARs? According to
the newer specs this should be possible...
I'm afraid, I have to investigate this problem further...
/Gabor
--
Gabor Herr [EMAIL PROTECTED]
Computer Science Department [EMAIL PROTECTED]
Darmstadt University of Technology
Germany
