Doug MacKenzie wrote:On my local server if I run the weblogic server through MyEclipse, and add the commons-logging-1.1.1.jar to the classpath I can get past this issue, but I can't do this in production.
That is most probably because eclipse will add the entire classpath while starting the weblogic instance.
Doug MacKenzie wrote:Any ideas on how to get past this without appending to the classpath?
Do you have the logging jar in your ear/war file? If yes, then you would not require it in weblogic's classpath.
In any case, its not a good idea to depend on the weblogic's classpath. All classes you need in your application, must be available within your application.
Since, it looks like a problem with configuring a J2EE application in weblogic, moving it to weblogic forum.