I'm using an exploded ear deployment layout in Weblogic to develop an app and after adding a new project to this old app, it won't deploy anymore, throwing a ClassNotFoundException when trying to load the actual application code from WEB/WEB-INF/classes.
The directory tree looks like this:
my_run | ---- EJB | ----META-INF | ----WEB | META-INF | WEB-INF | classes | lib
Before I started on this, my colleagues were deploying successfully with all the required jar libraries in the WEB/WEB-INF/lib directory and also copied into the Weblogic domain lib directory. I figured the EJBs were causing complexities because it is EJB2.0 legacy stuff.
This way of doing it now doesn't work for me and gives me an error that Hibernate could not be loaded when I launch the server or just the app. I then tried it with Hibernate in the Weblogic domain lib and then Spring could not be loaded.
I have spent the whole 8 hours today googling the issue and have read and tried pretty much everything that can be done with Weblogic, including weblogic jar prefs xml entries which gave very bizarre xml-related class casting issues.
I tried reducing it to basics and emptying the weblogic domain lib of everything except the JDBC jars and the stuff which is required by Weblogic security etc but I failed to find a solution.
I tried using in application.xml, didn't work.
I tried putting the Class-Path entries into the MANIFEST.MF with the same results.
Surely this is not so complicated?
I am now at the point where i have all the required jars both in the WEB-INF/lib dir and in the Weblogic domain lib and the app can't find its own Hibernate pojos.