[
https://issues.apache.org/activemq/browse/AMQNET-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63039#action_63039
]
Timothy Bish commented on AMQNET-290:
-------------------------------------
SNAPSHOT build is available at:
http://people.apache.org/~tabish/nms-1.5.0/
The current implementation would function the same whether its a local
transaction or a distributed transaction as that bit is transparent on the
client side. In either case the NMS client enlists as volatile as I can't make
enough sense out of the MS docs to see how recovery works so I can map it back
into the XA model that is required for interaction with ActiveMQ.
> Add an API model to NMS that allows providers to participate in Distributed
> Transactions.
> -----------------------------------------------------------------------------------------
>
> Key: AMQNET-290
> URL: https://issues.apache.org/activemq/browse/AMQNET-290
> Project: ActiveMQ .Net
> Issue Type: New Feature
> Components: NMS
> Affects Versions: 1.4.0
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Priority: Minor
> Fix For: 1.5.0
>
>
> Currently the NMS API doesn't define any way for the client to participate in
> distributed transactions. The JMS model allows a for this using the Java XA
> transactions. The JMS API defines an XAConnectionFactory, XAConnection, and
> XASession that provide the needed bits to interact with a Transaction Manager.
> We should provide something similar in NMS that allows for a provider library
> like NMS.ActiveMQ to be used in distributed transactions in .NET most likely
> using the MSDTC. The API could expose an IEnlistmentNotification
> implementation that allows the client to enlist the Transaction in a DTC
> controlled transaction as a Resource Manager.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
