[jira] Created: (AMQNET-93) NMS does not mirror standard 'JMS' exceptions

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.

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

Jim Gomes commented on AMQNET-93:
---------------------------------

I agree that we should be able to wrap orthogonal vendor exceptions into NMS exceptions.  Not sure how to handle exceptions that do not have a standard counterpart in NMS.  It will be incumbent upon the NMS provider implementer to funnel their specific vendor implementation exceptions into standard NMS exceptions.

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

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

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

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

Just a small note, as this is the only issue remaining in 1.0 and possibly holding up the 1.0 release, I'm fine with moving it to 1.1.

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

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

Jim Gomes updated AMQNET-93:
----------------------------

    Fix Version/s: 1.1
                       (was: 1.0)

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