-
Bug
-
Resolution: Answered
-
Low
-
None
-
None
-
Severity 3 - Minor
-
Specifically, ensure events are fired after a transaction has been successfully committed.
This ensures:
- Listeners will have no chance of preventing a commit during the handling of an event
- A Listener will always see data that has been successfully committed
The current pattern in Crucible is to fire the event, and then commit the transaction.
- causes
-
CRUC-6060 Work Day Plugin throwing an exception will cause the add comment transaction to be rolled back
- Closed
- relates to
-
CONFSERVER-30952 Event publisher should encapsulate work done in event listeners in a nested transaction scope
- Closed