The weblogic classpath has been locked down and can't be changed.
When hibernate instantiates a Configuration object it's throwing the following error:
I've checked the WEB-INF\lib folder and commons-logging-1.1.1.jar is present. 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. Any ideas on how to get past this without appending to the classpath?
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.
I'm not too familiar with Hibernate (yea, I can't believe it either), but I do know there are a number of hibernate properties that sometimes must be
explicilty specified when deploying to Weblogic.
Check your hibernate properties too make sure that everything is mapped properly as well as checking the config documentation to see what's available.
Maybe explicilty adding hibernate.session_factory_name or one of the others optionals will resolve the issue.
Also, and this depends on the design and intent of your app, if the missing lib is in your archive and if you can use the weblogic.xml descriptor specify