cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <>
Subject [jira] Commented: (CXF-2372) Allow JMS XAResource to participate in J2EE transaction
Date Fri, 31 Jul 2009 17:23:14 GMT


Daniel Kulp commented on CXF-2372:

The latest patch seems to be missing the "added" classes.  (JCATransactionalMessageListenerContainer,
XASingleConnectionFactory, etc..)  Can you redo the patch?

> Allow JMS XAResource to participate in J2EE transaction
> -------------------------------------------------------
>                 Key: CXF-2372
>                 URL:
>             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
> 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.

View raw message