activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Gomes (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AMQNET-69) Various DefaultMessageConverter issues
Date Wed, 09 Apr 2008 22:40:44 GMT

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

Jim Gomes resolved AMQNET-69.
-----------------------------

    Resolution: Fixed

Fixed by SVN revision 646581.

> Various DefaultMessageConverter issues
> --------------------------------------
>
>                 Key: AMQNET-69
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-69
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: MSMQ
>            Reporter: David Holroyd
>            Assignee: James Strachan
>             Fix For: 1.1
>
>         Attachments: DefaultMessageConverter_issues-patch.diff
>
>
> 1) {{ToMsmqMessage()}} does not handle the actual message body
> 2) {{answer.TimeToBeReceived = message.NMSExpiration}} seems to make the message expire
immediately (since the TimeSpan structure is initialised to 00:00:00)
> 3) {{answer.Label = message.NMSType}} raises an exception when NMSType is null (per AMQNET-67)
> 4) The MSMQ {{message.CorrelationId}}, {{message.DestinationQueue}} and {{message.TimeToBeReceived}}
properties all raise {{InvalidOperationException}} when accessed, if the message doesn't define
a value
> 5) Accessing the {{message.Body}} property raises an exception unless an {{IMessageFormatter}}
has been provided.
> The attached patch addresses these problems, but only provides support for BytesMessage
instances.  This seems better than no support for any kind of message though?  Made available
under ASF license.

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


Mime
View raw message