Uploaded image for project: 'CDI TCK'
  1. CDI TCK
  2. CDITCK-279

Ordering issue in CustomTransactionalObserverTest

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 1.1.0.Alpha3
    • 1.1.0.Alpha2
    • Tests
    • None

    Description

      Failed tests: testCustomTransactionalObserver(org.jboss.cdi.tck.tests.event.observer.transactional.custom.CustomTransactionalObserverTest): expected:<ActionSequence [data=[checkpoint, BEFORE_COMPLETION, AFTER_SUCCESS, AFTER_COMPLETION]]> but was:<ActionSequence [data=[checkpoint, BEFORE_COMPLETION, AFTER_COMPLETION, AFTER_SUCCESS]]>

      Transactional observer methods that declare one of the following transaction phases:

      AFTER_COMPLETION
      AFTER_SUCCESS
      AFTER_FAILURE

      are all executed in the "after completion phase" of the transaction. The difference is only in the outcome of the transaction. There is no ordering specified between AFTER_COMPLETION, AFTER_SUCCESS and AFTER_FAILURE notifications.

      The test incorrectly assumes that an AFTER_SUCCESS observer method must be notified before an AFTER_COMPLETION observer method which is a wrong assumption.

      Attachments

        Activity

          People

            mkouba@redhat.com Martin Kouba
            rhn-engineering-jharting Jozef Hartinger
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              PagerDuty