Vincent,
 
Thanks for your reply :)
 
First point: I guess you meant I should not have jars from my WEB-INF/lib in the weblogic classpath. I agree but it is unfortuantely not up to me...
Second point: yes it is strange but again, it is not up to me either... at least not for now.
 
I agree the first point is the only thing that might cause problems as far as I can see, and I can't do much about it.
 
I will keep you updated on this.
 
Emmanuel
----- Original Message -----
Sent: Monday, September 10, 2001 5:30 PM
Subject: Re: Classloader problems on Weblogic 6.02

Emmanuel,
 
I have not used WL 6.0 myself but several things look strange :
* You should normally not have any jar from the WEB-INF/lib directory of your webapp as they are loaded by special webapp class loaders,
* From the directory path below it seems your webapp is named "jsp", is that correct ? (just found it strange for a webapp name :) ). If your webapp is myproj then the WEB-INF directory should be directly below the myproj directory and not below the jsp one
 
Thanks
-Vincent
----- Original Message -----
Sent: Friday, August 10, 2001 4:36 PM
Subject: Re: Classloader problems on Weblogic 6.02

Still does not work. I am puzzled. The thing is (and you can see it on the stacktrace) that the ServletTestRedirector is deployed and working and the ServletTestCaller is found. The ServletTestCase is in the same jar file but is not found!?!?!?!
 
Here is more information on the classpaths
 
the weblogic class path is
 
java.class.path = /usr/local/weblogic/jdk130/jre/lib/rt.jar:/home/esciara/wlserver6.0:/usr/local/weblogic/wlserver6.0/lib/weblogic_sp.jar:/usr/local/weblogic/wlserver6.0/lib/weblogic.jar:/home/esciara/myproj/jsp/WEB-INF/lib/log4j.jar:/home/esciara/myproj/jsp/WEB-INF/lib/myproj_common.jar:/home/esciara/myproj/jsp/WEB-INF/lib/JRViewer.zip
 
in /home/esciara/myproj/jsp/WEB-INF/lib/ are the commons-cactus.jar, junit.jar and log4j.jar
 
Cactus sample classes are in /home/esciara/myproj/jsp/WEB-INF/classes
 
Anything ideas?
 
I tried adding commons-cactus.jar, junit.jar to the weblogic classpath, but then it is the sample org.apache.commons.cactus.sample.TestSampleServlet that is not found.
 
Emmanuel
 
----- Original Message -----
Sent: Monday, September 10, 2001 12:00 PM
Subject: Re: Classloader problems on Weblogic 6.02

Hi Emmanuel ... ! :-)
 
Good to hear from you. And glad you're using Cactus :-)
 
The message you're seeing comes from the server side. Can you check that you have all the needed jars (at the correct location) in your WAR file, as described in http://jakarta.apache.org/commons/cactus/getting_started.html ? If you do, could you drop the log4j jar as part of your WAR (in WEB-INF/lib) and run the test again. It will then generate a cactus_server.log file with useful information.
 
Also, I have much improved the generated logs and error messages in version 1.2, so I would suggest you download the latest nightly distribution before sending any log.
 
If I had to take a wild guess, I would say that you're missing the junit.jar file in your WEB-INF/lib directory ...
 
Thanks
-Vincent
 
P.S.: I'll call you to see how it goes. Now, this is support ! :-)
----- Original Message -----
Sent: Friday, August 10, 2001 11:43 AM
Subject: Classloader problems on Weblogic 6.02

Hi all, Hi Vincent, :)
 
I am trying to use Cactus on my project, which is using Weblogic 6.02 . I have a classloader problem: when I try the sample test using the swingui of junit 3.7, the error message at the end of my message is returned. The strange thing is that the ServletTestCaller class is found alright, but not the ServletTestCase... and they are at the same location... What am I missing?
 
 
java.lang.NoClassDefFoundError: org/apache/commons/cactus/ServletTestCase
 
 at java.lang.ClassLoader.defineClass0(Native Method)
 
 at java.lang.ClassLoader.defineClass(ClassLoader.java:486)
 
 at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:111)
 
 at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:304)
 
 at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:155)
 
 at java.lang.ClassLoader.loadClass(ClassLoader.java:297)
 
 at java.lang.ClassLoader.loadClass(ClassLoader.java:290)
 
 at java.lang.ClassLoader.loadClass(ClassLoader.java:253)
 
 at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:313)
 
 at java.lang.Class.forName0(Native Method)
 
 at java.lang.Class.forName(Class.java:120)
 
 at org.apache.commons.cactus.server.ServletTestCaller.callTestMethod(ServletTestCaller.java:102)
 
 at org.apache.commons.cactus.server.ServletTestCaller.doTest(ServletTestCaller.java:200)
 
 at org.apache.commons.cactus.server.ServletTestRedirector.doPost(ServletTestRedirector.java:149)
 
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:213)
 
 at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:1265)
 
 at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1631)
 
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
 
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 
Cheers
 
Emmanuel

Reply via email to