This week's book giveaway is in the Mac OS forum.
We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line!
See this thread for details.
The moose likes JPA Certification (OCEJPA) and the fly likes doubt about PostRemove and PostUpdate events Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Certification » JPA Certification (OCEJPA)
Bookmark "doubt about PostRemove and PostUpdate events" Watch "doubt about PostRemove and PostUpdate events" New topic
Author

doubt about 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 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.
 
GeeCON Prague 2014
 
subject: doubt about PostRemove and PostUpdate events