KnowledgeHub
Questions
Tags
Users
Search
Alex Rivera
|
Logout
Edit Question
Title
Body
I am currently working with @PostPersist and @PostUpdate , and in those triggers I am persisting additional entities. The question is, are those triggers in the same transaction and if not is it possible to force it ? For me it works this way. While I was looking through the logs the transaction isn't existing ( it's commited just before the trigger is launched ) which prevents me ( without REQUIRES_NEW on the persisting method from injected bean ) from saving the additional entities in database. REQUIRED attribute is totally ignored, and MANDATORY attribute do not throw an exception. Can it be the problem with JUnit ( since I am in the dev. phase and did not test the behavior on full env. ) ? If extending the transaction on this triggers is not possible, how to ensure that if the rollback occurs before the @PostPersist and @PostUpdate , those operations also will be rollbacked.
Tags (comma-separated)
Save Edits
Cancel