Uploaded image for project: 'Crucible'
  1. Crucible
  2. CRUC-6061

Audit all event handling code in Crucible

    XMLWordPrintable

Details

    Description

      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.

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. CRUC-6060 Work Day Plugin throwing an exception will cause the add comment transaction to be rolled back

          • Medium - Medium priority issues
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. CONFSERVER-30952 Event publisher should encapsulate work done in event listeners in a nested transaction scope

          • Low - Low priority issues
          • Closed

          Activity

            People

              Unassigned Unassigned
              npellow Nick
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: