activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQCPP-362) Make Session and MessageConsumer both Startable and Stoppable in the CMS API
Date Sat, 16 Apr 2011 15:50:05 GMT

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

Timothy Bish resolved AMQCPP-362.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 3.4.0

Fixed in trunk

> Make Session and MessageConsumer both Startable and Stoppable in the CMS API
> ----------------------------------------------------------------------------
>
>                 Key: AMQCPP-362
>                 URL: https://issues.apache.org/jira/browse/AMQCPP-362
>             Project: ActiveMQ C++ Client
>          Issue Type: Improvement
>          Components: CMS Impl
>    Affects Versions: 3.3.0
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>            Priority: Trivial
>             Fix For: 3.4.0
>
>
> In order to allow users to more safely shut down CMS resources we should add the startable
and stoppable interface to Session and MessageConsumer in CMS so that the user doesn't need
to cast inner types.  The will be marked as optional methods in CMS and can throw cms::UnsupportedOperation
exceptions if not implemented.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message