[
https://issues.apache.org/jira/browse/AMQNET-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16951656#comment-16951656
]
Michael Andre Pearce edited comment on AMQNET-622 at 10/15/19 6:42 AM:
-----------------------------------------------------------------------
I am worried. Openwire is not dead, there is activity in the community slow but
there is.
NMS is litterally meant to be a one to one with JMS spec api.
There are otherways to achieve your goal without changing a spec api. After all
its been acheived in java fine with the same apis
was (Author: michael.andre.pearce):
I am worried.
NMS is litterally meant to be a one to one with JMS spec api
There are otherways to achieve your goal without changing a spec api
> IConnection event listeners are not invoke on reconnect
> -------------------------------------------------------
>
> Key: AMQNET-622
> URL: https://issues.apache.org/jira/browse/AMQNET-622
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: AMQP
> Reporter: Chris Morgan
> Priority: Major
>
> I found the Apache.NMS.AMQP.NMSConnection allows applications to add
> ConnectionInterruptedListeners and ConnectionResumedListeners however these
> event callbacks are never invoked even during failover/reconnect.
> The NMS AMQP provider does have a INmsConnectionListener to handle the
> interrupted and resumed connection events so its unclear whether
> ConnectionInterruptedListeners and ConnectionResumedListeners are not
> supported in favour for the INmsConnectionListener or if the
> ConnectionInterruptedListeners and ConnectionResumedListeners need to be
> invoked in addition to the INmsConnectionListener events.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
