Romain Manni-Bucau wrote > That's a pretty big and important change. > > I'd keep it for +0.1.x (just my opinion) > >> If possible, please include TOMEE-664 >> <https://issues.apache.org/jira/browse/TOMEE-664> in the 1.5.2 >> release.
After looking at the diffs for that change, I believe that it actually is included in the 1.5.2 branch. I tried to delete my comment before anyone saw it, but apparently I was too late. However, I have an issue that sounded like the same one that it resolved: I have an EAR containing a number of EJB jars and one WAR file. There are a number of jar files needed by several of the EJB jars that are in the lib directory. One of those jars in the lib directory contains a persistence.xml file and associated class files. When I deploy the ear to the 1.5.2 snapshot, the persistence context initializes twice, the second initialization is apparently in conjunction with the loading of the war file. Unfortunately, this results in the ReloadableEntityManagerFactory.delegate not being initialized when I try to use it later, resulting in an NPE. When I deploy the ear to the 1.6.0 snapshot, everything works fine. I don't know which JIRA Issue fixed the problem in the trunk, but I would like that fix included in the 1.5.2 release. Thanks, ----- - Tim -- View this message in context: http://openejb.979440.n4.nabble.com/Availability-of-1-5-2-snapshots-tp4661139p4661244.html Sent from the OpenEJB User mailing list archive at Nabble.com.
