Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <538243874.1235751359423.JavaMail.jira@brutus>
Date: Fri, 27 Feb 2009 08:15:59 -0800 (PST)
From: "Jim Gomes (JIRA)" <jira+amqnet@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Work started: (AMQNET-93) NMS does not mirror standard 'JMS'
 exceptions
In-Reply-To: <1612440838.1216239600322.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/activemq/browse/AMQNET-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on AMQNET-93 started by Jim Gomes.

> 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.