You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Nathan Mittler (JIRA)" <ji...@apache.org> on 2007/04/05 21:13:35 UTC
[jira] Created: (AMQCPP-96) Setting property "JMSXGroupID" on a
stomp message yields IllegalArgumentException
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: Nathan Mittler
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.
[jira] Commented: (AMQCPP-96) Setting property "JMSXGroupID" on a
stomp message yields IllegalArgumentException
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38962 ]
Timothy Bish commented on AMQCPP-96:
------------------------------------
I've fixed the problem in trunk. I want to take a look and make sure there aren't anymore headers that should go.
> 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: Nathan Mittler
> 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.
[jira] Resolved: (AMQCPP-96) Setting property "JMSXGroupID" on a
stomp message yields IllegalArgumentException
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Assigned: (AMQCPP-96) Setting property "JMSXGroupID" on a
stomp message yields IllegalArgumentException
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish reassigned AMQCPP-96:
----------------------------------
Assignee: Timothy Bish (was: Nathan Mittler)
> 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.