Normally, I would recommend 2) and decouple the entities from any EE or Web tier so you can use them anywhere as well as SE junit test them.

If you follow the structure of the examples directory – you will see an example of 2)

However, I since your persistence.xml and entities are both off of the classes classloader – I would expect this to be ok. I normally work with jars in the EAR where the model jar is separate from the ejb.jar and the war jar. There is a use case for application managed deployments putting everything off the app-inf folder.

I will look more into the spring use case when I have more time later today or tomorrow and get back to you – as I find all possible deployment scenarios of high interest.

I completely switched to the Spring DI and got rid of EJB: configuring Spring and EJB proved to be too complicated and besides the rest of the application is using Spring configuration.

What you are telling me about the CNFE exception makes a lot of sense. I thought I should be fine: I deploy the application as an exploded EAR directory; my entity classes are in APP-INF/classes of the exploded EAR; my persistence.xml is in APP-INF\classes\META-INF.

Hi, I will look into your spring configuration when I get back into the office later today.

If you switch from EE container managed spec development to VMWare spring development – your configuration could change in several ways depending on whether you are running the spring DI container in your WAR or EJB container.

From a quick look on my IPhone, the CNFE exception is due to the persistence unit and entity classes being in different classloaders. The weaving exception I will need to look at. Normally the EJB container proxy handles this without Spring.

Thank you for your help on trying to make JPA 2 / EclipseLink 2 to work on Weblogic 10.3.4. I have been able to persuade my superiors to move to WebLogic 12.1.1.

However, I am having a bit of a problem trying to deploy my persistence.xml. I have changed my design a bit. Now, instead of an EJB I am using a Spring configured DAO class (I am integrating my piece into a larger Spring-configured application). I use the same entities. I believe my problem is due to the Spring configuration.