activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <jira+amq...@apache.org>
Subject [jira] [Commented] (AMQNET-340) MessagePropertyIntercepter is intercepting too many properties
Date Tue, 23 Aug 2011 18:26:29 GMT

    [ https://issues.apache.org/jira/browse/AMQNET-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13089645#comment-13089645
] 

Timothy Bish commented on AMQNET-340:
-------------------------------------

Best way to help is to create an NUnit test case that demonstrates the issue so it can be
added to the set of tests. 

> MessagePropertyIntercepter is intercepting too many properties
> --------------------------------------------------------------
>
>                 Key: AMQNET-340
>                 URL: https://issues.apache.org/jira/browse/AMQNET-340
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: NMS
>    Affects Versions: 1.5.0
>         Environment: .NET
>            Reporter: Matthew Good
>            Assignee: Jim Gomes
>            Priority: Minor
>
> The class MessagePropertyIntercepter claims is is redirecting the setting of "NMS Properties"
to class properties instead of adding them to the Properties list.  The problem is that it
redirects more than NMS Properties - it redirects any property name that exists on the class.
 So properties like "CorrelationId" get redirected.  If I set a property called "Text" on
a TextMessage it overwrites the message body.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message