EclipseLinkJpaDialect does not support declarative transaction isolation [SPR-12319]

[spring-projects-issues]

Senén de Diego opened SPR-12319 and commented

EclipseLinkJpaDialect throws an exception in beginTransaction when specifying a transaction isolation level other than default in the @Transactional annotation.

The same problem has been solved (under certain circumstances) in the last RC for HibernateJpaDialect.

Would it be possible to fix this also?

---

Affects: 4.1.1

Issue Links:

• Isolation support for JPA with Hibernate EntityManager 4 [SPR-11942] #16559 Isolation support for JPA with Hibernate EntityManager 4
• Spring's JDBC connection access disables shared cache in EclipseLink [SPR-7753] #12409 Spring's JDBC connection access disables shared cache in EclipseLink
• OpenJpaDialect does not support declarative transaction isolation [SPR-12333] #16938 OpenJpaDialect does not support declarative transaction isolation

Referenced from: commits de11cd8, 33d85d2, bd5383e

[spring-projects-issues]

Juergen Hoeller commented

Addressed along the lines of http://stackoverflow.com/questions/24293945/spring-managed-transactions-eclipselink-jpa-custom-isolation-level now, to be available in the upcoming 4.1.2 snapshot.

Juergen

[spring-projects-issues]

Senén de Diego commented

That was fast!. Thank you.

[spring-projects-issues]

Juergen Hoeller commented

If you have a chance, please give this a try with a recent 4.1.2.BUILD-SNAPSHOT (see http://projects.spring.io/spring-framework/)... There's another EclipseLinkJpaDialect change (#12409) going with it, would be great to test that as well :-)

Juergen