Actually the thing that worked for me (every single time) is placing the
Tester and Tested jar files in {javahome}/jre/lib/ext. Of course, that's
TOTALLY wrong and can really screw with your system so please don't try it.
:)
By the way, Daniel, I'm using Tomcat. How do I add stuff to the server
classpath?
----- Original Message -----
From: "Daniel Hoppe" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, May 23, 2001 5:25 PM
Subject: AW: Cactus/Weblogic
Hi Phil, yepp, I had lot's of classpath problems too. I don't know what
exactly is happening, but I suppose jUnit is doing some crazy classloader
introspection stuff, the instantiation exception is a classnotfoundexception
which was not reported properly in my case. What I came up with (not nice
but works for me) is:
- Put cactus and junit into your server classpath
- Don't package cactus and junit into the war file (strange enough...)
- Put the test case classes into the war file
- Put the test case classes into the server classpath as well
I know that this sounds kind of strange, but this works for me (took me 2
days to figure this out). I can send you my ant testfile if you like, maybe
that helps.
Daniel
-----Urspr�ngliche Nachricht-----
Von: Phil Magill [mailto:[EMAIL PROTECTED]]
Gesendet: Mittwoch, 23. Mai 2001 10:53
An: [EMAIL PROTECTED]
Betreff: Cactus/Weblogic
Hello,
Has anyone had any classpath problems running Cactus in Weblogic 6. Weblogic
is starting correctly and deploying. The error i'm getting is
javax.servlet.ServletException: Error "instanciating" class
[com.whatever.......]. The test classes are build into a war file that has
been deployed ???????????
Thanks
Phil
