You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cactus-dev@jakarta.apache.org by ji...@apache.org on 2004/04/17 18:39:32 UTC
[jira] Updated: (CACTUS-10) NoSuchMethodError in BaseLog.
The following issue has been updated:
Updater: Vincent Massol (mailto:vmassol@apache.org)
Date: Sat, 17 Apr 2004 9:38 AM
Changes:
description changed from Using the log4j-core.jar supplied with the Binary install of Cactus 2.2 I
receive the following error when executing the Sample application task of
"tests_tomcat_32". The specific exception occurs in the "tests" task.
I can only assume that it has to do with invoking the static method
getInstance(String) of the Log4j's Category class.
Interestingly, when I hypothesized that maybe the log4j-core.jar was corrupt
somehow and replaced it with the current log4j-core.jar (1.1.3) I received a the
exception "NoClassDefFoundError" as it looks for org.apache.log4j.Logger in the
org.apache.commons.cactus.util.log.LogService.getLog(String). I then downloaded
the Cactus source and cannot even find a reference to a class named "Logger" in
the LogService class. Also, the log4j-core.jar supplied with the Binary install
does in fact have a org.apache.log4j.Logger class file.
Something is REALLY messed up in either the sample application, the
log4j-core.jar that it uses or in the way Cactus uses Log4J. to Using the log4j-core.jar supplied with the Binary install of Cactus 2.2 I
receive the following error when executing the Sample application task of
"tests_tomcat_32". The specific exception occurs in the "tests" task.
I can only assume that it has to do with invoking the static method
getInstance(String) of the Log4j's Category class.
Interestingly, when I hypothesized that maybe the log4j-core.jar was corrupt
somehow and replaced it with the current log4j-core.jar (1.1.3) I received a the
exception "NoClassDefFoundError" as it looks for org.apache.log4j.Logger in the
org.apache.commons.cactus.util.log.LogService.getLog(String). I then downloaded
the Cactus source and cannot even find a reference to a class named "Logger" in
the LogService class. Also, the log4j-core.jar supplied with the Binary install
does in fact have a org.apache.log4j.Logger class file.
Something is REALLY messed up in either the sample application, the
log4j-core.jar that it uses or in the way Cactus uses Log4J.
environment changed from Operating System: Windows NT/2K
Platform: PC to Operating System: Windows NT/2K
Platform: PC
priority changed to Major
Fix Version changed to 1.2
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/CACTUS-10?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/CACTUS-10
Here is an overview of the issue:
---------------------------------------------------------------------
Key: CACTUS-10
Summary: NoSuchMethodError in BaseLog.<init>
Type: Bug
Status: Reopened
Priority: Major
Project: Cactus
Components:
Servlet Sample
Fix Fors:
1.2
Versions:
1.1
Assignee: Vincent Massol
Reporter: Houston Pagtakhan
Created: Fri, 21 Sep 2001 8:11 AM
Updated: Sat, 17 Apr 2004 9:38 AM
Environment: Operating System: Windows NT/2K
Platform: PC
Description:
Using the log4j-core.jar supplied with the Binary install of Cactus 2.2 I
receive the following error when executing the Sample application task of
"tests_tomcat_32". The specific exception occurs in the "tests" task.
I can only assume that it has to do with invoking the static method
getInstance(String) of the Log4j's Category class.
Interestingly, when I hypothesized that maybe the log4j-core.jar was corrupt
somehow and replaced it with the current log4j-core.jar (1.1.3) I received a the
exception "NoClassDefFoundError" as it looks for org.apache.log4j.Logger in the
org.apache.commons.cactus.util.log.LogService.getLog(String). I then downloaded
the Cactus source and cannot even find a reference to a class named "Logger" in
the LogService class. Also, the log4j-core.jar supplied with the Binary install
does in fact have a org.apache.log4j.Logger class file.
Something is REALLY messed up in either the sample application, the
log4j-core.jar that it uses or in the way Cactus uses Log4J.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org