You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Seumas Soltysik (JIRA)" <ji...@apache.org> on 2009/07/30 16:46:14 UTC

[jira] Updated: (CXF-2372) Allow JMS XAResource to participate in J2EE transaction

     [ https://issues.apache.org/jira/browse/CXF-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Seumas Soltysik updated CXF-2372:
---------------------------------

    Attachment: CXF-2372.patch

> Allow JMS XAResource to participate in J2EE transaction
> -------------------------------------------------------
>
>                 Key: CXF-2372
>                 URL: https://issues.apache.org/jira/browse/CXF-2372
>             Project: CXF
>          Issue Type: Improvement
>          Components: Integration
>    Affects Versions: 2.2.2
>            Reporter: Seumas Soltysik
>         Attachments: CXF-2372.patch
>
>
> The submitted patch provides the capability for a JMS XAResource to participate in the J2EE transaction when used in the context of the JCA adapater. Using transaction APIs defined by the JCA adapater spec, the JMS transport will register an XAResource associated with a JMSSession with the JCA connector, which will in turn enroll the XAResource in a transaction with the J2EE transaction manager. In order to facilitate the registering of the XAResoure, the JCA adapter must pass information via the Bus to the JMS transport. The JMS transport is then responsible for creating a MessageEndpoint and initiating a transaction by calling MessageEndpoint.beforeDelivery() and then closing the transaction by calling MessageEndpoint.afterDelivery()
> See section 12.5.6 of the JCA specification for more details regarding these semantics.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.