activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AMQCPP-96) Setting property "JMSXGroupID" on a stomp message yields IllegalArgumentException
Date Fri, 06 Apr 2007 14:22:35 GMT

     [ 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.


Mime
View raw message