[cdi-dev] [JBoss JIRA] (CDI-722) backward incompatible change for BEFORE_COMPLETION

Mark Struberg (JIRA) issues at jboss.org
Fri Feb 2 15:30:00 EST 2018

Mark Struberg created CDI-722:

             Summary: backward incompatible change for BEFORE_COMPLETION
                 Key: CDI-722
                 URL: https://issues.jboss.org/browse/CDI-722
             Project: CDI Specification Issues
          Issue Type: Bug
          Components: Java EE integration
    Affects Versions: 2.0 .Final
            Reporter: Mark Struberg

The split from the original documentation to a SE+EE doc did introduce a backward incompatibility to CDI-1.2, CDI-1.1 and CDI-1.0.

The CDI-2.0 spec states in 24.1.2:

24.1.2. Observer method invocation context in Java EE
When Running in Java EE, the container must extend the rules defined in Observer method invocation context and must also ensure that all kinds of observers are called in the same client security context as the invocation of Event.fire() or Event.fireAsync() or BeanManager.fireEvent().

Whereas older CDI specs are defined as:
If the observer method is a before completion transactional observer method, it is called within the context of the transaction that is about to complete and with the same client security context and lifecycle contexts.

With other words, in the older specs the security context was always the same context of the operation which calls the final commit operation. 
The change in CDI-2.0 is thus a backward incompatible wording.

This message was sent by Atlassian JIRA

More information about the cdi-dev mailing list