Surely a classloader issue. Normally we enrich the classloader with this jar but you are using a custom classloader so it is surely ignored. So solution is to use the spring way: all in the app. Le 6 août 2015 11:34, "Mike Spencer" <[email protected]> a écrit :
> Also, when I copy/pasted the OpenEJBServerPlatform class into my project > and used that, the transactions started working. So it seems like if I use > the correct eclipselink.target-server property transactions are working. > Now I just need to figure out why it isn't being found when using the TomEE > libraries. > > - Mike Spencer > > On 08/06/2015 01:30 PM, Mike Spencer wrote: > >> Late reply, but it appears that you are using the same interface. I >> copy/pasted the 4.7.2 version of OpenEJBServerPlatform < >> http://grepcode.com/file/repo1.maven.org/maven2/org.apache.openejb/openejb-jpa-integration/4.7.2/org/apache/openejb/jpa/integration/eclipselink/OpenEJBServerPlatform.java/> >> into my project and used the >> 'org.apache.openejb.jpa.integration.eclipselink.OpenEJBServerPlatform' >> target-server JPA property without issues, but it would not work unless I >> included it in my project. The openejb-jpa-integration package in TomEE is >> 4.7.2, so I am not sure where the difference is. I did this after upgrading >> to TomEE 1.7.2 from 1.7.1, so it doesn't seem like an issue that was fixed >> in the minor release. >> >> - Mike Spencer >> >> On 07/28/2015 10:35 AM, Romain Manni-Bucau wrote: >> >>> Hmm >>> >>> Blind try from phone but is our platform implementing the right >>> interface? >>> Know hibernate happily broke it super often so maybe eclipselink did as >>> well. >>> Le 28 juil. 2015 17:18, "Mike Spencer"<[email protected]> a >>> écrit : >>> >>> I just tried that target-server and the application fails on deployment >>>> due to a NoSuchMethodException >>>> >>>> >>>> Exception Description: Failed to instantiate ServerPlatform of type >>>> [org.apache.openejb.jpa.integration.eclipselink.OpenEJBServerPlatform] >>>> specified in [eclipselink.target-server] property. >>>> Internal Exception: java.lang.NoSuchMethodException: >>>> >>>> org.apache.openejb.jpa.integration.eclipselink.OpenEJBServerPlatform.<init>(org.eclipse.persistence.sessions.DatabaseSession) >>>> at >>>> >>>> org.eclipse.persistence.exceptions.EntityManagerSetupException.predeployFailed(EntityManagerSetupException.java:230) >>>> ... 63 more >>>> >>>> I looked at the OpenEJBServerPlatform class definition via javap and it >>>> had the correct constructor. >>>> >>>> - Mike Spencer >>>> >>>> >>>> On 07/27/2015 05:03 PM, Romain Manni-Bucau wrote: >>>> >>>> yes looks TxMgr setup is fine >>>>> >>>>> Eclipselinks is the default in glassfish and surely more integrated >>>>> than in tomee, maybe the issue is just this >>>>> >>>>> FYI in tomee we have a specific platform server for eclipselinks: >>>>> >>>>> jpaProperties.put("eclipselink.target-server", >>>>> >>>>> "org.apache.openejb.jpa.integration.eclipselink.OpenEJBServerPlatform"); >>>>> >>>>> >>>>> >>>>> Romain Manni-Bucau >>>>> @rmannibucau<https://twitter.com/rmannibucau> | Blog >>>>> <http://rmannibucau.wordpress.com> | Github< >>>>> https://github.com/rmannibucau> | >>>>> LinkedIn<https://www.linkedin.com/in/rmannibucau> | Tomitriber >>>>> <http://www.tomitribe.com> >>>>> >>>>> >> >
