Try log4j version 1.2.3. Depending on how WL sets the Thread Context Loader you might not need to do anything. This is 1.2.3 only.
Let us know if it works. At 11:55 30.05.2002 -0700, Andrew Tumpach wrote: >Hi all, > >I've created a couple custom appenders, but when deployed with my app on >WebSphere, I realized I have a classpath issue: Log4J is on the JVM >classpath, >but the app is not. Therefore, Log4J cannot see these custom appenders. > >Our admins (for good reasons) may be hesitant to allow applications to be on >the JVM classpath. Log4J can't be moved to application classpaths instead of >JVM because it is used by EJBs in some projects. > >Does anyone else know of alternate solutions? > >Thanks, >Andrew -- Ceki SUICIDE BOMBING - A CRIME AGAINST HUMANITY Sign the petition: http://www.petitiononline.com/1234567b I am signatory number 22106. What is your number? -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
