activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "james strachan (JIRA)" <j...@apache.org>
Subject [jira] Moved: (AMQNET-5) IsAdvisory method of ActiveMQDestination incorrectly returns False for Advisory messages
Date Tue, 27 Feb 2007 10:39:04 GMT

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

james strachan moved AMQ-1037 to AMQNET-5:
------------------------------------------

        Fix Version/s:     (was: 4.1.1)
                       1.0
          Component/s:     (was: NMS (C# client))
    Affects Version/s:     (was: 4.x)
                  Key: AMQNET-5  (was: AMQ-1037)
              Project: ActiveMQ .Net  (was: ActiveMQ)

> IsAdvisory method of ActiveMQDestination incorrectly returns False for Advisory messages
> ----------------------------------------------------------------------------------------
>
>                 Key: AMQNET-5
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-5
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>         Environment: Using latest SVN checkout of DotNetClient
>            Reporter: Stuart Bain
>            Priority: Minor
>             Fix For: 1.0
>
>         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.


Mime
View raw message