David,
David Blevins wrote: > > Sorry it's taken be a bit to get back to this. > Not a show stopper, still LOVE OpenEJB, and I appreciate your looking into it at all. I'm as much wondering whether I'm breaking any rules deploying an 'SE app' to an 'EE server', and can easily EJB-ify my DAOs if/when I need to. David Blevins wrote: > > Where is the jar that contains > org.eclipse.persistence.jpa.PersistenceProvider and where is the jar > that contains > org.eclipse.persistence.transaction.JTATransactionController? > I tried two packaging 'flavors'. The First stab was the Galileo 'standard wizard' which deploys 4 jars, one of which is the JPA API. So after deploying normally I deleted the deployed API jar and started the server. In this scenario both of those classes are in a jar named org.eclipse.persistence.core_1.1.2.v20090612-r4475.jar Second stab was to download and unzip the 'single jar packaging' from http://www.eclipse.org/eclipselink/downloads/ Same result, and again both classes do exist in the eclipselink.jar that lives under the eclipselink/jlib folder. David Blevins wrote: > > Seems the issue occurs possibly because the EclipseLink > PersistenceProvider class cannot see (or sees a version from the wrong > classloder) its JTATransactionController class. > Can't say I completely understand how all the pieces fit together. My war has a resource_local persistence-unit with the DAOs using EntityTransactions. And aside from the initial exception in the openejb.log, run flawlessly. Is the JTATransactionController class load an OpenEJB boostrap requirement? Here's a sample war with the eclipselink.jar if you'd like to look into it further... http://www.nabble.com/file/p24996863/daosample.war daosample.war Thanks, Jim -- View this message in context: http://www.nabble.com/Eclipselink-JPA-RESOURCE_LOCAL-PersistenceUnit-with-Tomcat-embedded-tp24746512p24996863.html Sent from the OpenEJB User mailing list archive at Nabble.com.
