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 2010/02/09 19:45:32 UTC
[jira] Updated: (AMQNET-210) NMS Exceptions to follow Microsoft
Guidelines.
[ https://issues.apache.org/activemq/browse/AMQNET-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Gomes updated AMQNET-210:
-----------------------------
Fix Version/s: 1.3.0
Remaining Estimate: 1 hour
Original Estimate: 1 hour
> NMS Exceptions to follow Microsoft Guidelines.
> ----------------------------------------------
>
> Key: AMQNET-210
> URL: https://issues.apache.org/activemq/browse/AMQNET-210
> 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 - http://msdn.microsoft.com/en-us/library/ms229064.aspx 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).
> https://fisheye.springsource.org/browse/spring-net/trunk/test/Spring/Spring.Core.Tests/ExceptionsTest.cs#r357
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.