You are viewing a plain text version of this content. The canonical link for it is here.

Posted to java-dev@axis.apache.org by bu...@apache.org on 2003/04/16 21:52:30 UTC

DO NOT REPLY [Bug 19090] New: - Weblogic Deployment, log4j, commons-logging.jar

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19090>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19090

Weblogic Deployment, log4j, commons-logging.jar

           Summary: Weblogic Deployment, log4j, commons-logging.jar
           Product: Axis
           Version: 1.1rc2
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Deployment / Registries
        AssignedTo: axis-dev@ws.apache.org
        ReportedBy: jens@void.fm


Some Bea versions don't like multiple "." in library names, so axis deployment will fail with a log4j ClassNotFoundException even the jar is in the proper lib/ location. Renaming log4j-x.x.x.jar to log4j.jar seems to help.

Another issue is  the Manifest Classpath: Entry in commons-logging.jar. As someone reported earlier weblogic deployment fails with a StringIndexOutOfBoundsException.
I could still reproduce the problem on WebLogic Server 6.1 SP4  11/08/2002 21:50:43 #221641.

See
http://marc.theaimsgroup.com/?l=axis-user&m=103347880202479&w=2