You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OpenJPA is barely maintained these days and has not caught up with JPA 2.1 in three years (!) ... Even TomEE 7 - as the sole remaining OpenJPA stakeholder - recently went GA without updating OpenJPA either, recommending EclipseLink along the lines of WebSphere 8.5/9.0 instead.
Since the latest OpenJPA 2.4.1 still causes issues in a Java 8 based build, in particular with its Java 6 limited annotation processor, let's remove our dedicated OpenJPA support right away. If it ever gets updated to JPA 2.1 (which is unlikely), it will still work as a standard JPA provider.
Note that there is a discussion about that at #20584... As per my comment there, I'm inclined to expect a corresponding JpaVendorAdapter to be shipped with OpenJPA itself, or a corresponding extension living in the OpenJPA project at Apache.
In quite a few areas, we ship two reference integrations out of the box and expect others to provide integration on their end: FreeMarker + Groovy for templating, EhCache + Caffeine for caching, Hibernate and EclipseLink for deep JPA integration. For JPA specifically, there's the additional constraint that all common application servers out there include Hibernate or EclipseLink in the meantime, with even IBM having given up on OpenJPA and shipping EclipseLink instead now.
Of course, OpenJPA 3.0 should work fine with standard JPA 2.1 integration in Spring, i.e. simply without a JpaVendorAdapter, just like DataNucleus does as well (which we never shipped an adapter for). If anything does not work out of the box there, please raise it in a separate ticket; we'll sort it out ASAP.
Juergen Hoeller opened SPR-14426 and commented
OpenJPA is barely maintained these days and has not caught up with JPA 2.1 in three years (!) ... Even TomEE 7 - as the sole remaining OpenJPA stakeholder - recently went GA without updating OpenJPA either, recommending EclipseLink along the lines of WebSphere 8.5/9.0 instead.
Since the latest OpenJPA 2.4.1 still causes issues in a Java 8 based build, in particular with its Java 6 limited annotation processor, let's remove our dedicated OpenJPA support right away. If it ever gets updated to JPA 2.1 (which is unlikely), it will still work as a standard JPA provider.
Issue Links:
The text was updated successfully, but these errors were encountered: