[
https://issues.apache.org/activemq/browse/AMQNET-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50445#action_50445
]
Jim Gomes commented on AMQNET-93:
---------------------------------
The naming convention for the exceptions has been changed to not include the
NMS* prefix on the classes... except for NMSException, NMSConnectionException,
and NMSSecurityException, as requested. These were the existing exceptions and
therefore are "grandfathered" in. All new exceptions will not start with NMS
as part of the class name.
Related discussion on this topic can be found in this Nabble thread:
[http://www.nabble.com/Discuss%3A-AMQNET-93-to22255094.html]
> NMS does not mirror standard 'JMS' exceptions
> ---------------------------------------------
>
> Key: AMQNET-93
> URL: https://issues.apache.org/activemq/browse/AMQNET-93
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: EMS
> Affects Versions: 1.0
> Reporter: Mark Pollack
> Assignee: Jim Gomes
> Fix For: 1.1
>
> Attachments: NMS_Exception.patch
>
>
> The JMS spec defines several exception classes and these are not mirrored in
> the NMS API.
> In particular this came up as I would like to specifically catch
> TransactionRolledBackException. I know that TIBCO EMS this exception class
> and perhaps more. How to handle vendor exceptions outside the spec other
> then wrapping and checking for inner exception types?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
