0

The desire is to catch OLE instead of SOSE to be less tightly coupled to hibernate in case we ever needed to change JPA providers.

The case that is producing the exception is very straightforward; i've breakpointed just before a versioned entity update is committed, committed a change directly in the db, and then allowed execution to continue.

It looks like from StaleObjectStateException vs OptimisticLockException that the answer should just be "use JPA annotations", but we are doing that. Specifically, the Entity in question imports annotations only from javax.persistence.*

Community
  • 1
  • 1
Personman
  • 2,324
  • 1
  • 16
  • 27

1 Answers1

0

It turns out this was because we were using hibernate Session objects rather than EntityManagers - Hibernate doesn't check for JPA annotations (and wrap SOSEs in OLEs if they are present) unless an EntityManager is being used.

We can't fix it because DropWizard uses Sessions, but now that we understand why this is happening and that it will happen consistently, we can just catch the SOSE and the issue is resolved.

Personman
  • 2,324
  • 1
  • 16
  • 27