jakarta-cactus-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fred Loney" <lo...@spiritedsw.com>
Subject Re: NoSuchMethodError in JUnitVersionHelper constructor
Date Sat, 24 Aug 2002 19:58:29 GMT
Update: problem is that the webapp used an earlier aspectjrt.jar
version. Updating the jars to the versions required by cactus fixed this
problem.

----- Original Message -----
From: "Fred Loney" <loney@spiritedsw.com>
To: "Cactus Users List" <cactus-user@jakarta.apache.org>
Sent: Saturday, August 24, 2002 11:22 AM
Subject: NoSuchMethodError in JUnitVersionHelper constructor


> Running cactus 1.4 produces the message:
>
>
warning(junit.framework.TestSuite$1)junit.framework.AssertionFailedError
> : Exception in constructor: testCreate (java.lang.NoSuchMethodError
>  at
>
org.apache.cactus.util.JUnitVersionHelper.<clinit>(JUnitVersionHelper.ja
> va;org/apache/cactus/util/log/LogAspect.java(1k):73)
>  at
org.apache.cactus.AbstractTestCase.<init>(AbstractTestCase.java:124)
>  at
>
org.apache.cactus.AbstractWebTestCase.<init>(AbstractWebTestCase.java:86
> )
>  at org.apache.cactus.ServletTestCase.<init>(ServletTestCase.java:119)
> ...
>
> The method testCreate exists in the test class. The test case runs
> under cactus 1.2. Failure occurs after upgrade to cactus 1.4. All
> configs
> and deployment libs painstakingly verified. This is perhaps yet
another
> manifestation of the Curse of the Clever Classloader: every new
release
> of a tool that uses clever introspection tricks invariably breaks a
> non-trivial enterprise deployment in some extremely subtle manner
> because of classloader conflicts. This necessitated a 3-day bug hunt
> for myself and others when upgrading to cactus 1.2. I have a perfectly
> normal deployment, with perhaps one hitch: aspectjrt.jar is used in
the
> webapp classloader rather than the web classloader. cactus.jar and the
> non-aspect dependent jars are in the web classloader.
>
> A starting point is to understand exactly where this message
originated:
> a log message, a wrapped exception, a junit assertion, a
> NoSuchMethodError trace? What does the parenthesized line signify
(it's
> not a standard stack trace line)? What does (1k) in LogAspect.java(1k)
> signify? Why is the fatal error tagged as a warning? How can I
configure
> cactus so that it prints a normal stack trace?
>
> Any clues to help isolate the cause are appreciated.
>
>
>


--
To unsubscribe, e-mail:   <mailto:cactus-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:cactus-user-help@jakarta.apache.org>


Mime
View raw message