[prev in list] [next in list] [prev in thread] [next in thread]
List: activemq-dev
Subject: [jira] Commented: (AMQNET-93) NMS does not mirror standard 'JMS'
From: "Timothy Bish (JIRA)" <jira+amqnet () apache ! org>
Date: 2009-02-27 19:49:59
Message-ID: 1398722304.1235764199484.JavaMail.jira () brutus
[Download RAW message or body]
[ https://issues.apache.org/activemq/browse/AMQNET-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50101#action_50101 \
]
Timothy Bish commented on AMQNET-93:
------------------------------------
I'd have to agree with Yev, adding the NMS preface to everything seems overkill, and \
negates the point of having things in the NMS namespace since that really should \
serve to sufficiently identify that the object is part of NMS. Keeping it on \
NSMException and NMSSecurityException seems fine since they map to JMS types and \
present a more familiar facade to those familiar with JMS, but adding to everything \
that's not an interface seems a bit overkill.
> 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.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic