|
Hi
Vincent,
thanks
! That explains it.
But do
you have any idea about the errors I still get when I run the sample
tests, with only our log4j, and not with the one coming with
Cactus, like so:
[junit] Running
org.apache.cactus.sample.TestSampleServlet
[junit] Tests
run: 12, Failures: 0, Errors: 12, Time elapsed: 0.297 sec
[junit] Testsuite:
org.apache.cactus.sample.TestSampleServlet
[junit] Tests
run: 12, Failures: 0, Errors: 12, Time elapsed: 0.297 sec
[junit]
[junit] Testcase: testGetMethod took 0.265
sec
[junit] Caused an
ERROR
[junit]
org/apache/log4j/Logger
[junit]
java.lang.NoClassDefFoundError: org/apache/log4j/Logger
[junit] at
org.apache.cactus.util.log.LogService.getLog(LogService.java:173)
[junit] at
org.apache.cactus.AbstractTestCase.runBare(AbstractTestCase.java:366)
[junit] at
junit.framework.TestResult$1.protect(TestResult.java:106)
[junit] at
junit.framework.TestResult.runProtected(TestResult.java:124)
[junit] at
junit.framework.TestResult.run(TestResult.java:109)
[junit] at
junit.framework.TestCase.run(TestCase.java:131)
[junit] at
junit.framework.TestSuite.runTest(TestSuite.java:173)
[junit] at junit.framework.TestSuite.run(TestSuite.java,
Compiled Code)
[junit] at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java,
Compiled Code)
[junit] at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java,
Compiled Code)
[junit]
[junit]
Testcase: testPostMethod took 0 sec
[junit] Caused an ERROR
[junit]
org.apache.log4j.Category: method
getInstance(Ljava/lang/String;)Lorg/apache/log4j/Logger; not
found
[junit] java.lang.NoSuchMethodError:
org.apache.log4j.Category: method
getInstance(Ljava/lang/String;)Lorg/apache/log4j/Logg
; not
found
[junit] at
org.apache.cactus.util.log.BaseLog.<init>(BaseLog.java:83)
[junit] at
org.apache.cactus.util.log.LogService.getLog(LogService.java:178)
[junit] at
org.apache.cactus.AbstractTestCase.runBare(AbstractTestCase.java:366)
[junit] at
junit.framework.TestResult$1.protect(TestResult.java:106)
[junit] at
junit.framework.TestResult.runProtected(TestResult.java:124)
[junit] at
junit.framework.TestResult.run(TestResult.java:109)
[junit] at
junit.framework.TestCase.run(TestCase.java:131)
[junit] at
junit.framework.TestSuite.runTest(TestSuite.java:173)
[junit] at junit.framework.TestSuite.run(TestSuite.java,
Compiled Code)
[junit] at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java,
Compiled Code)
[junit] at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java,
Compiled Code)
[junit]
Thank
you,
Heikki
Hi Heikki,
The file log4j-gump.jar contains the gump suffix
because GUMP renames the log4j.jar file after it builds it every day. So, to
answer your question, the log4j-gump.jar is supposed to be the
*latest* possible build of the Log4j project. Cactus uses the normal log4j
distribution (not modified in whatsoever manner) ...
What must have happened is that this class was
introduced after the last Log4j release and this is why you don't have it in
release 1.1.3. However, if you are careful to put only your log4j jar in the
classpath (and not the ones from Cactus) everything should work fine as Cactus
does not make use of this internal Logger class. Cactus only uses the Category
class.
Thanks
-Vincent
----- Original Message -----
Sent: Monday, September 24, 2001 2:23
PM
Subject: Log4j gump
I've traced my problem to this:
our web app needs log4j.jar. However, our log4j.jar is not the same
as the one used by Cactus. Specifically the class Logger is not in our
log4j.jar.
The log4j.jar that comes with Cactus (log4j-gump) contains a.o. a
class Logger. This class is not in the log4j.jar we're using, and neither is
it in the log4j distribution on the log4j website (version 1.1.3), http://jakarta.apache.org/log4j/docs/download.html.
Does Cactus use a modified or older version of log4j ? Or am I
missing something completely here ?
Any tips welcome !
Thanks,
Heikki Doeleman
From: Vincent Massol
[mailto:[EMAIL PROTECTED]]
Sent: Friday, September 21, 2001 2:22
PM
To: [EMAIL PROTECTED]
Subject: Re:
Sample application in nightly build
You're right, it is optional. What I
understand from your message is that you are indeed using Log4j but your
own version that does not have the Log4j Logger class (is that an old
version ?). I've just checked the nightly zip and it is slightly wrong
(I have asked the persons managing the nightly builds to modify that).
The log4j-gump.jar jar is simply the log4j.jar one but
renamed.
The error you're getting is a class not
found, which means it is *not* in your classpath or at least the correct
classpath ! Don't forget there are 2 classpaths : the one from your
webapp and the one from the junit test runner.
Thanks
-Vincent
----- Original Message -----
Sent: Friday, September 21, 2001
12:41 PM
Subject: RE: Sample application
in nightly build
But on the Cactus web site it is stated that including log4j is
optional !
In the log4j.jar that we use there is no class Logger; it is
however in log4j-gump.jar that comes with the cactus distribution. I
do have log4j-gump.jar in my CLASSPATH ..
Thanks
Heikki
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/
|
