You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Jim Gomes (JIRA)" <ji...@apache.org> on 2009/11/20 21:03:52 UTC
[jira] Work started: (AMQNET-148) Wrap provider implementation
exceptions into standard NMS exceptions
[ https://issues.apache.org/activemq/browse/AMQNET-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on AMQNET-148 started by Jim Gomes.
> Wrap provider implementation exceptions into standard NMS exceptions
> --------------------------------------------------------------------
>
> Key: AMQNET-148
> URL: https://issues.apache.org/activemq/browse/AMQNET-148
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: EMS
> Affects Versions: 1.0.0, 1.1.0
> Reporter: Jim Gomes
> Assignee: Jim Gomes
> Priority: Minor
> Fix For: 1.2.0
>
>
> The EMS provider supports additional exception types beyond the standard NMS types. These should be handled in a seamless extensible manner.
> As reported by Mark Pollack: "Just for completeness the list of exception in EMS that don't map are AuthenticationExcetpion, CannotProceedException, CommunicationException, ConfigurationException, InvalidNameException, ServiceUnavailableException."
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.