Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
8.0.7, 8.0.8, 8.0.9, 8.0.10, 8.0.11
Description
A Java web application is unable to use the default EclipseLink JPA provider that is included in the TomEE Plume distributable. JPA is only able to discover the OpenJPA provider within the TomEE server libraries. Attached TestWeb application to reproduce the issue. This configuration was working in TomEE Plume 8.0.6, and behavior was changed in 8.0.7.
Web application persistence.xml configured with EclipseLink JPA:
<persistence-unit name="TestJPA" transaction-type="RESOURCE_LOCAL"> <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
JPA fails to load with error:
javax.persistence.PersistenceException: No persistence providers available for "TestJPA" after trying the following discovered implementations: org.apache.openjpa.persistence.PersistenceProviderImpl
Workaround 1:
Copy the the EclipseLink library into the web application libraries. Then JPA will discover both the OpenJPA and EclipseLink providers from the Java web application.
Workaround 2:
Append CATALINA_OPTS with JVM property "openejb.classloader.filterable-resources" using default value excluding "META-INF/services/javax.persistence.spi.PersistenceProvider":
-Dopenejb.classloader.filterable-resources=META-INF/services/javax.validation.spi.ValidationProvider,META-INF/services/javax.ws.rs.client.ClientBuilder,META-INF/services/javax.json.spi.JsonProvider,META-INF/services/javax.cache.spi.CachingProvider,META-INF/javamail.default.providers,META-INF/javamail.default.address.map,META-INF/javamail.charset.map,META-INF/mailcap,org/slf4j/impl/StaticLoggerBinder.class
