activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (Resolved) (JIRA)" <jira+amq...@apache.org>
Subject [jira] [Resolved] (AMQNET-348) Add new Event points in ISession for Transaction Begin, Commit and Rollback notification
Date Wed, 16 Nov 2011 16:09:51 GMT

     [ https://issues.apache.org/jira/browse/AMQNET-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Timothy Bish resolved AMQNET-348.
---------------------------------

    Resolution: Fixed

Fix applied in trunk along with tests for AMQ and Stomp providers
                
> Add new Event points in ISession for Transaction Begin, Commit and Rollback notification
> ----------------------------------------------------------------------------------------
>
>                 Key: AMQNET-348
>                 URL: https://issues.apache.org/jira/browse/AMQNET-348
>             Project: ActiveMQ .Net
>          Issue Type: New Feature
>          Components: ActiveMQ, NMS, Stomp
>    Affects Versions: 1.5.0, 1.5.1
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>            Priority: Minor
>             Fix For: 1.6.0
>
>
> Add three new events in the ISession interface to allow client to be notified when a
Transaction has begin when its committed or when its rolled back.  This is mainly useful in
the DTC aware NetTxSession to inform clients that the DTC transaction has completed and its
safe to close or perform other operations on the Session.  It can also allow a client to log
more information etc.
> We can define a delegate in ISession for this
> {noformat}
>     public delegate void SessionTxEventDelegate(ISession session);
> {noformat}
> And add three event points for the notifications
> {noformat}
>     event SessionTxEventDelegate TransactionStartedListener;
>     event SessionTxEventDelegate TransactionCommittedListener;
>     event SessionTxEventDelegate TransactionRolledBackListener;
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message