Hi, that's probably the fix making the persistence.xml in webapp for ear being picked and managing the resolution between webapp and lib part of the ear (different persistence.xml, same persistence unit name)
i don't really know when it was imported in 1.5.2 but it can't be part of the 1.5.2 IMO since it can really change the behavior of applications *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/3/5 ymaraner <[email protected]> > Testing my application against recent snapshots of 1.5.2 results in a > NullPointerException: > > I have an EAR containing several EJB jars and one WAR file. > There are a number of jar files needed by most 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 it is > used by a startup bean to retrieve cmp entity beans, resulting in an NPE. > > The same ear file deploys and initializes successfully to the > 1.6.0.SNAPSHOT. > > If I remove the war from the ear, it deploys and initializes fine to the > 1.5.2.SNAPSHOT. > > 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/NullPointerException-in-ReloadableEntityManagerFactory-createEntityManager-1-5-2-SNAPSHOT-tp4661255.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
