Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <14164912.1175869355096.JavaMail.jira@brutus>
Date: Fri, 6 Apr 2007 07:22:35 -0700 (PDT)
From: "Timothy Bish (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Resolved: (AMQCPP-96) Setting property "JMSXGroupID" on a
 stomp message yields IllegalArgumentException
In-Reply-To: <3035429.1175800415443.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


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

Timothy Bish resolved AMQCPP-96.
--------------------------------

    Resolution: Fixed

Fixed in trunk and in the 2.0 tag.

> Setting property "JMSXGroupID" on a stomp message yields IllegalArgumentException
> ---------------------------------------------------------------------------------
>
>                 Key: AMQCPP-96
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-96
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>    Affects Versions: 1.1, 2.0
>            Reporter: Nathan Mittler
>         Assigned To: Timothy Bish
>            Priority: Minor
>             Fix For: 2.0
>
>
> We have defined all of the standard stomp headers as well as AMQ extensions as predefined stomp headers.  This causes an IllegalArgumentException for settting any of these properties.  We currently have no other way to set the AMQ extension for JMSXGroupID, yet it also can't be set via setStringProperty().
> We should see how the AMQ Java code handles the AMQ-specific properties and try to model our code after that.

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