[
https://issues.apache.org/activemq/browse/AMQNET-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=49987#action_49987
]
Timothy Bish commented on AMQNET-93:
------------------------------------
I'd recommend that on this one we have the vendor NMS impl libraries wrap
exceptions that don't map to the Standard JMS / NMS exception types in the
NMSException. In the JMS Spec the JMSException is used "if the JMS provider
fails to send the message due to some internal error" which I think applies
here as well. The NMS Exception thrown from the vendor could contain the
vendor exception as the inner exception and if the client app wants to check
for those it can otherwise it remains less coupled to the NMS implementation's
vendor API.
> 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
>
>
> 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.
