activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Holroyd (JIRA)" <>
Subject [jira] Created: (AMQNET-69) Various DefaultMessageConverter issues
Date Mon, 01 Oct 2007 22:55:22 GMT
Various DefaultMessageConverter issues

                 Key: AMQNET-69
             Project: ActiveMQ .Net
          Issue Type: Bug
          Components: MSMQ
            Reporter: David Holroyd
            Assignee: James Strachan
         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

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

View raw message