[ https://issues.apache.org/jira/browse/AMQNET-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Gomes updated AMQNET-290: ----------------------------- Component/s: ActiveMQ > Add an API model to NMS that allows providers to participate in Distributed > Transactions. > ----------------------------------------------------------------------------------------- > > Key: AMQNET-290 > URL: https://issues.apache.org/jira/browse/AMQNET-290 > Project: ActiveMQ .Net > Issue Type: New Feature > Components: ActiveMQ, 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. - For more information on JIRA, see: http://www.atlassian.com/software/jira