commons-logging has a habit of being able to find Log4j using classloader
tricks, but then not being able to actually use it afterwards because they don't
exist in classloaders that are normally visible to each other except via
classloader tricks. I think there needs to be two way communication be
I had to put mine in the container classpath in one of the init files -
it had something to do with the init and the application classpath not
being enough. It's been a while, but if you need details, I could
probably dig them up.
Alison Ortega
North Carolina State University
ACS
Systems Program
The log4j-1.2.8.jar is simply included in the WAR file in WEB-INF/lib.
If I take it out of there the application deploys successfully, if I
leave it in I get the exception below.
I am using the commons-logging api, which should then delegate logging
to log4j, so I'm not calling log4j methods d
Where are you defining the log4j.jar in your classpath?
Alison Ortega
North Carolina State University
ACS
Systems Programmer II
919-513-1417
>>> [EMAIL PROTECTED] 6/22/2004 11:02:12 AM >>>
Hi,
I have a problem deploying a war file containing log4j1.2.8.jar on
weblogic 8.1 sp2 running on RedHat
Quoting Keith <[EMAIL PROTECTED]>:
> Hi,
>
> I have a problem deploying a war file containing log4j1.2.8.jar on
> weblogic 8.1 sp2 running on RedHat kernal version 2.4.21-4
>
> The strange thing is it deploys fine on tomcat, and weblogic running on
> windows. Just loses it when I try to deploy
