Skip to content

Drop native OpenJPA support [SPR-14426] #18997

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
spring-projects-issues opened this issue Jul 4, 2016 · 3 comments
Closed

Drop native OpenJPA support [SPR-14426] #18997

spring-projects-issues opened this issue Jul 4, 2016 · 3 comments
Assignees
Labels
in: data Issues in data modules (jdbc, orm, oxm, tx) type: task A general task
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

spring-projects-issues commented Jul 4, 2016

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:

@spring-projects-issues
Copy link
Collaborator Author

Maxim Solodovnik commented

Hello,

 

OpenJPA 3.0.0 was recently released (JPA 2.1 compatible)
Would it be possible to get OpenJPA support back?

@spring-projects-issues
Copy link
Collaborator Author

spring-projects-issues commented Aug 8, 2018

Juergen Hoeller commented

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.

@spring-projects-issues
Copy link
Collaborator Author

Maxim Solodovnik commented

Everything seems to work,

Thanks a lot for clarifications!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: data Issues in data modules (jdbc, orm, oxm, tx) type: task A general task
Projects
None yet
Development

No branches or pull requests

2 participants