dn-issue-optimistic-locking-jpa
JPA Test case demonstrating an issue I reported to DataNucleus JPA Provider folks: datanucleus/datanucleus-rdbms#307
In a nutshell, enabling field-based Optimistic Locking (using a Version-annotated field) along with the Level2 Cache disabled did not work with DataNucleus, due to a weird NullPointerException (yup, the billion dollar one! ;)): Exception thrown while loading remaining rows of query
This test case contains a set of Maven profiles that run the same tests against other JPA providers. The tests pass as expected with EclipseLink and Hibernate, but not with DataNucleus.
-
To run the tests against DataNucleus (default profile):
mvn clean compile testormvn clean compile test -P datanucleus -
To run the tests against EclipseLink:
mvn clean compile test -P eclipselink -
To run the tests against Hibernate:
mvn clean compile test -P hibernate