activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Gomes (JIRA)" <>
Subject [jira] Resolved: (AMQNET-210) NMS Exceptions to follow Microsoft Guidelines.
Date Tue, 09 Feb 2010 21:21:33 GMT


Jim Gomes resolved AMQNET-210.

    Resolution: Fixed

Added serialization to all NMS exceptions.  The exceptions now adhere to as many of the guidelines
as possible.  It is not possible for them to adhere to the naming guideline of not including
the word "Exception" in the name of the type as the names are already decided upon and are
not changing.

> NMS Exceptions to follow Microsoft Guidelines.
> ----------------------------------------------
>                 Key: AMQNET-210
>                 URL:
>             Project: ActiveMQ .Net
>          Issue Type: Improvement
>          Components: NMS
>    Affects Versions: 1.1.0
>            Reporter: Mark Pollack
>            Assignee: Jim Gomes
>            Priority: Trivial
>             Fix For: 1.3.0
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
> There are some conventions around the signatures that should be present in .NET exceptions
- summarizes them.  In particular the
one regarding serialization in my experience ends of being requested at some point.   The
current NMS Exceptions do not provide the signature for serialization.  I can across this
while trying to enforce this 'exception convention' unit test in Spring.NET.  See here (it
originally came from the NAnt code base). 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message