[cdi-dev] [JBoss JIRA] (CDI-213) Specify what happens if an observer method does directly initiate, commit or rollback JTA transaction

[Tom Jenkinson (JIRA)]

    [ https://issues.jboss.org/browse/CDI-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12714194#comment-12714194 ] 

Tom Jenkinson commented on CDI-213:
-----------------------------------

When I composed my initial response I was under the impression that the event consumer was async sorry. If an event consumer is more like an EJB RPC then flowing the transaction should be fine.

Its not clear to me if there are more event consumer types than, IN_PROGRESS, perhaps there are async event consumer types also?

If the app is already using JTA and you make any synchronous in memory call on the same thread the transaction should be available "out-of-the-box" anyway.
                
> Specify what happens if an observer method does directly initiate, commit or rollback JTA transaction
> -----------------------------------------------------------------------------------------------------
>
>                 Key: CDI-213
>                 URL: https://issues.jboss.org/browse/CDI-213
>             Project: CDI Specification Issues
>          Issue Type: Clarification
>          Components: Events, Java EE integration
>            Reporter: Martin Kouba
>            Assignee: Pete Muir
>            Priority: Minor
>             Fix For: 1.1.PRD
>
>
> At the moment, the specification does not really specify what happens if an observer method does directly initiate, commit or rollback JTA transaction.
> See *10.5. Observer notification*: "An observer method may not directly initiate, commit or rollback JTA transactions."

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira