Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Fri, 1 Jul 2011 20:47:28 +0000 (UTC)
From: "Timothy Bish (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: 
 <1682605152.9702.1309553248539.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Closed] (AMQ-2242) ActiveMQDestination options are not
 marshalled using openwire v3
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Timothy Bish closed AMQ-2242.
-----------------------------

       Resolution: Won't Fix
    Fix Version/s:     (was: 5.6.0)

The uri options are client specific and there's no plan to include them with the marshalled message.

> ActiveMQDestination options are not marshalled using openwire v3
> ----------------------------------------------------------------
>
>                 Key: AMQ-2242
>                 URL: https://issues.apache.org/jira/browse/AMQ-2242
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.2.0
>            Reporter: Kyle Anderson
>            Priority: Minor
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Set setPhysicalName() in ActiveMQDestination parses destination options off the passed physical name string; ActiveMQDestinationMarshaller only marshalls boolean properties and the modified physical name.  The map of destination options is lost in the process.  The destination options are extremely useful when writing broker filter plugins.

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