check out: http://www.theserverside.com/resources/articles/ClassLoading/article.html It speaks about j2ee 1.3 class loading scheme and the implementations provided by weblogic 6.1 SP2, WebSphere 4.0, and HP-AS 8. In it there is discussion of adding ejb dependant jars into the jar manifest class-path.
Hope this helps, Matt -----Original Message----- From: Andrew Tumpach [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 30, 2002 2:55 PM To: [EMAIL PROTECTED] Subject: Extending appenders, classpath issues 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 __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
