[
https://issues.apache.org/activemq/browse/AMQNET-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62817#action_62817
]
Timothy Bish commented on AMQNET-290:
-------------------------------------
Things are a bit tricky on .NET in that the System.Transactions classes can be
in Local or Distributed mode depending on the configuration of the client. For
distributed transactions we really need to be able to map the DTC id's into
Xid's but MS seems to have made this pretty tough in .NET. When in local mode
what should we do, just play nice and use standard local transactions or refuse
to play altogether. This implies that we'd have to manage the enlistment
though since in local mode we can't do recovery so we'd have to be sure we are
enlisted as volatile.
> 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.
