This week's book giveaway is in the Big Data forum.
We're giving away four copies of Elasticsearch in Action and have Radu Gheorghe & Matthew Lee Hinman on-line!
See this thread for details.
The moose likes EJB and other Java EE Technologies and the fly likes doubt about JPA PostRemove and PostUpdate events Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Elasticsearch in Action this week in the Big Data forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "doubt about JPA PostRemove and PostUpdate events" Watch "doubt about JPA PostRemove and PostUpdate events" New topic
Author

doubt about JPA PostRemove and PostUpdate events

Paul.J Wong
Greenhorn

Joined: Apr 25, 2013
Posts: 7
Hi everyone,

I have a doubt about PostRemove and PostUpdate events in JPA. I am reading the Pro JPA 2 book, on page 327, it states "When the SQL for deletion of an entity finally does get sent to the database, the PostRemove event will get fired. As with the PostPersist lifecycle event, the PostRemove event does not guarantee success. The enclosing transaction may still be rolled back".

As I learned, transaction can either commit, or rollback. In the sentence, if the deletion SQL does get sent to the database, that means the transaction is already committed, how come it may still be rolled back?

Thanks in advance.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: doubt about JPA PostRemove and PostUpdate events