[
https://issues.apache.org/activemq/browse/AMQNET-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50100#action_50100
]
Yev Bronshteyn commented on AMQNET-93:
--------------------------------------
Jim,
I'm not clear on the renaming... the only exception in NMS that has the NMS
prefix (aside from NMSException) is NMSSecurityException... so the convention
is not well established. I would suggest, therefore, not entrenching an
unfortunate convention. I call it unfortunate for two reasons:
* First, the NMS prefix is redundant with the NMS namespace, the namespaces
being the preferred way of identifying what goes with what.
* Second, Microsoft's .Net framework guidelines
(http://msdn.microsoft.com/en-us/library/ms229043.aspx), dictate not
capitalizing all letters of 3+letter acronyms (hence XmlException instead of
XMLException).
So at this point, an ounce of inconsistency with ourselves seems somewhat
preferable to a pound of poor naming (or 28.35 g and .45 kg, for the
metrically-minded :-)).
> 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.
