You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "james strachan (JIRA)" <ji...@apache.org> on 2007/02/26 19:25:02 UTC

[jira] Updated: (AMQ-1037) IsAdvisory method of ActiveMQDestination incorrectly returns False for Advisory messages

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

james strachan updated AMQ-1037:
--------------------------------

    Fix Version/s:     (was: 4.1.2)
                   4.1.1

> IsAdvisory method of ActiveMQDestination incorrectly returns False for Advisory messages
> ----------------------------------------------------------------------------------------
>
>                 Key: AMQ-1037
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1037
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: NMS (C# client)
>    Affects Versions: 4.x
>         Environment: Using latest SVN checkout of DotNetClient
>            Reporter: Stuart Bain
>            Priority: Minor
>             Fix For: 4.1.1
>
>         Attachments: ActiveMQDestination.patch
>
>
> The IsAdvisory method of the ActiveMQDestination class incorrectly returns False for all advisory messages.
> The advisory flag is only set when the ActiveMQDestination(name) constructor is used - but the ActiveMQTopicMarshaller.CreateObject method uses the ActiveMQDestination() constructor so the flag is never set.
> The attached patch sets the advisory flag when the PhysicalName setter is called which fixes the problem.

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