qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tomas Restrepo (JIRA)" <qpid-...@incubator.apache.org>
Subject [jira] Commented: (QPID-246) Custom Exception types should be serializable
Date Fri, 05 Jan 2007 16:51:27 GMT

    [ https://issues.apache.org/jira/browse/QPID-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462530
] 

Tomas Restrepo commented on QPID-246:
-------------------------------------

Noticed that the original patch misses a bunch of custom exception classes (as they were derived
from others). Submitting a second patch that complements the first one to fix the remaining
exception classes. Hopefully this gets all of them.

> Custom Exception types should be serializable
> ---------------------------------------------
>
>                 Key: QPID-246
>                 URL: https://issues.apache.org/jira/browse/QPID-246
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Dot Net Client
>         Environment: .NET 1.1
>            Reporter: Tomas Restrepo
>            Priority: Minor
>         Attachments: SerializableExceptions.diff
>
>
> The custom Exception types defined by the .NET client should be serializable to ensure
the client is easy to use from as many environments as possible. This is pretty important
if used in contexts where COM interop is involved, including Enterprise Services.
> This involves:
> - Adding [Serializable] attributes to exception classes
> - Implementing a serialization constructor
> - Implemente ISerializable.GetObjectData() if needed.
> Patch to fix this follows.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message