Title:
that's probably because you've removed the log4j jar from your classpath ... :-)
----- Original Message -----
Sent: Friday, September 21, 2001 12:36 PM
Subject: RE: Sample application in nightly build

Getting there though not quite yet :)
I've modified CLASSPATH which I guess would solve the ServletTestResult error I got. However I still found two other references to apache.commons.cactus instead of apache.cactus (in my web.xml and redirector.jsp). I changed these to get rid of the 'commons'. The effect I'm having now is that when I try to start the web server, it says
 
 Exception in thread "main" java.lang.NoSuchMethodError: org.apache.log4j.Category: method getInstance(Ljava/lang/String
;)Lorg/apache/log4j/Logger; not found
        at org.apache.cactus.util.log.BaseLog.<init>(BaseLog.java:83)
        at org.apache.cactus.util.log.LogService.getLog(LogService.java:178)
        at org.apache.cactus.server.ServletTestRedirector.<clinit>(ServletTestRedirector.java:89)
        at java.lang.Class.newInstance0(Native Method)
        at java.lang.Class.newInstance(Class.java:241)
        at org.apache.tomcat.core.ServletWrapper.loadServlet(ServletWrapper.java:268)
        at org.apache.tomcat.core.ServletWrapper.init(ServletWrapper.java:289)
        at org.apache.tomcat.context.LoadOnStartupInterceptor.contextInit(LoadOnStartupInterceptor.java, Compiled Code)
        at org.apache.tomcat.core.ContextManager.initContext(ContextManager.java, Compiled Code)
        at org.apache.tomcat.core.ContextManager.init(ContextManager.java, Compiled Code)
        at org.apache.tomcat.startup.Tomcat.execute(Tomcat.java:195)
        at org.apache.tomcat.startup.Tomcat.main(Tomcat.java:235)
 
 
Any suggestions ??
Thanks !
Heikki

-----Original Message-----
From: Vincent Massol [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 21, 2001 1:13 PM
To: [EMAIL PROTECTED]
Subject: Re: Sample application in nightly build


Hi Heikki,

ServletTestResult has never been a public API that you use in your tests. It
has been renamed internally to WebTestResult but you shouldn't care. If you
have a problem of class not found, it simply means that you are mixing the
jars from Cactus 1.1 with those from 1.2 in your classpath (either client
side or server side).

Thanks
-Vincent

----- Original Message -----
From: Heikki Doeleman
To: '[EMAIL PROTECTED]'
Sent: Friday, September 21, 2001 11:44 AM
Subject: RE: Sample application in nightly build

Hi,

I not only installed the newer distribution jar, but also the newer sample
app, where all package names have already been updated.

The funny thing is that if I do a search on files containing text or being
named ServletTestResult, the only places it is found are the old
commons-cactus.jar files. And neither in Cactus files nor in our web app do
I find any references to the file ServletTestResult. But I do get that
ClassNotFoundException ..

Thanks
Heikki



-----Original Message-----
From: Rakesh Bhalla [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 21, 2001 12:34 PM
To: [EMAIL PROTECTED]
Subject: Re: Sample application in nightly build


Hello,

--- Heikki Doeleman <[EMAIL PROTECTED]> wrote:
> Hi
>
> I have tried installing Cactus 1.2 from the nightly build download
> (jakarta-cactus-22-20010919.zip). However, trying to run the sample
> app,
> starting the TestAll class, all tests fail with errors like
>
> java.lang.ClassNotFoundException:
> org.apache.commons.cactus.ServletTestResult
  Cactus 1.1 had all its packages and classes as the following tree:

org.apache.commons.cactus.*
   org.apache.commons.cactus.util.* ... etc.

   from Cactus 1.2 onwards it has  been changed to
org.apache.cactus.*
   org.apache.cactus.util.* ... etc.

Please note the missing 'commons' there. So try opening up the source
file again that you mentioned and make the package change mentioned
above and let us know what happened next.

=====
Thanks.
Rakesh Bhalla.

__________________________________________________
Terrorist Attacks on U.S. - How can you help?
Donate cash, emergency relief information
http://dailynews.yahoo.com/fc/US/Emergency_Information/

Reply via email to