activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Pollack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQNET-93) NMS does not mirror standard 'JMS' exceptions
Date Fri, 18 Jul 2008 22:05:02 GMT

    [ https://issues.apache.org/activemq/browse/AMQNET-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44395#action_44395
] 

Mark Pollack commented on AMQNET-93:
------------------------------------

Just to clarify, do you plan to mirror the current list of standard JMS exceptions in NMS?

As for non-standard exceptions, perhaps wrap it in UnknownVendorException to the caller has
an indication to do something special?  

Just for completeness the list of exception in EMS that don't map are  AuthenticatoinExcetpion,
CannotProceedExceptin, CommunicationException, ConfigurationException, InvalidNameException,
ServiceUnavailableException.  



> 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: James Strachan
>             Fix For: 1.0
>
>
> 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.


Mime
View raw message