Websphere has a rather complex class loading mechanism. See for example http://www.theserverside.com/resources/article.jsp?l=ClassLoading
In your particular case, shouldn't the Class-Path directive read: Class-Path: lib/log4j-1.2.6.jar lib/ I think the trailing slash (/) is required. Let us know if this helps. At 15:01 22.08.2002 -0700, you wrote: >Hi all, > >I'm currently using log4j 1.2.6 and here is the >envrionment: for development, I'm using WSAD 4.0.3 and >for production we have WebSphere App Sever 4.03. I >have an ejb project and a web project under one >enterprise application project within WSAD. I use >Struts as our presentation framework and Session EJBs >for business layer. Here is my problem with using >log4j within WSAD: > >I have log4j configured separately for the web module >and ejb module and I'm able to logging sucessfully >using the default initialization. But for ejb module, >I'm having problem reading the configuration file. My >understanding is that, WSAD 4.0.3 test envrionment is >in compliant with the J2EE classloading standard. So >I put both log4j.jar and log4j.properties in the /lib >directory of the enterprise application project and >also has an entry in the manifest file of the ejb >project: > >Manifest-Version: 1.0 >Class-Path: lib/log4j-1.2.6.jar /lib > >The classes are loaded sucessfully, but the >log4j.properties file can not seem to be loaded. I >have an io exception stating that log4j.properties can >not be found when I run my app. Did anyone come across >the same problem? Any insight will be greatly >appreicated!! > >Thanks, -- Ceki -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
