I've done this and it didn't work for me. My example put commons-logging.jar in the root of the ear, and the Manifest.mf file in my war referred to it like this:
Class-Path: commons-logging.jar Same problem everyone else has mentioned. I believe this is a specific problem with the WebLogic classloader, not a struts or commons logging problem. -Ryan -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 12, 2002 8:38 AM To: [EMAIL PROTECTED] Subject: Re: WebLogic 6.1SP2 with Struts 1.1b-1 Mark, Have you tried packaging it as a J2EE app instead of a Web app? app.ear | |-webApp.war | |-META-INF | | | |-application.xml | |-lib | |-commons-logging.jar You would need to provide a manifest file for webApp.war that contained the following: Class-Path: lib/commons-logging.jar The application.xml file would look something like this: <!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN" "http://java.sun.com/dtd/application_1_3.dtd";> <application> <display-name>My Application</display-name> <module> <web> <web-uri>webApp.war</web-uri> <context-root>webApp</context-root> </web> </module> </application> I haven't played around with 1.1 or commons logging, but this approach has solved some other class loading issues I've had with WL. Just a thought... -- Kris Schneider <mailto:[EMAIL PROTECTED]> D.O.Tech <http://www.dotech.com/> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
