[
https://issues.apache.org/jira/browse/CXF-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737667#action_12737667
]
William Tam commented on CXF-2372:
----------------------------------
Any reason why the TheadLocal is not cleared in the same finally block in
receiveAndExecute()? I'm afraid it might be possible that onMessage() is not
reached (due to some exception) and the ThreadLocal could result in not being
cleared. Also, I would check for null "ep" in the finally block.
> 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
> Assignee: Daniel Kulp
> Attachments: CXF-2372.patch, CXF-2372.patch2, CXF-2372.patch3
>
>
> 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.
