Skip to content
This repository has been archived by the owner on Jun 9, 2020. It is now read-only.

Test case highlighting an NPE in DataNucleus while trying to use field-based Optimistic Locking with the Level2 Cache disabled

Notifications You must be signed in to change notification settings

rm3l/dn-issue-optimistic-locking-jpa

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

53 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

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 test or mvn 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

About

Test case highlighting an NPE in DataNucleus while trying to use field-based Optimistic Locking with the Level2 Cache disabled

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 3

  •  
  •  
  •  

Languages