Hi Heiko, Instead of creating/deleting LockEntity, have a boolean state field isLocked. Set/unset it as the application logic demands always flush on mutation always refresh on access.
But why a separate entity, why not using database locks itself? ----- Pinaki Poddar Chair, Apache OpenJPA Project -- View this message in context: http://openjpa.208410.n2.nabble.com/OpenJPA-1-2-EntityExistsException-on-em-persist-for-Entity-that-is-no-longer-present-in-DB-tp6819702p6821041.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
