You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2015/06/19 19:58:00 UTC
[jira] [Closed] (AMQ-5779) Message Properties that contain dashes
silently fail with selectors
[ https://issues.apache.org/jira/browse/AMQ-5779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish closed AMQ-5779.
-----------------------------
Resolution: Not A Problem
This is working as it should, the dash value is treated as a minus as per selector syntax. The names need to match those defined in the JMS Spec rules.
> Message Properties that contain dashes silently fail with selectors
> -------------------------------------------------------------------
>
> Key: AMQ-5779
> URL: https://issues.apache.org/jira/browse/AMQ-5779
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.11.1
> Reporter: ocean
>
> If you attempt to use a message property whose name contains a '-' (dash) then any selector on that property will never match. EG:
> 1. Subscribe to a queue with the selector:
> {code}
> (node-id = 'node1')
> {code}
> 2. Now publish to the queue and set the string property:
> {code}
> response.setStringProperty("node-id", "node1");
> {code}
> This will never match. If you remove the dashes and change the property to something like "NodeId" then everything works peachy keen.
> Few problems with this behavior:
> # Not clear if this is in compliance with the spec. The requirements around Identifiers specified in the spec say nothing about '-' being an illegal character.
> # If AMQ can't handle dashes for whatever reason the system should fail fast the moment a selector containing a property with dashes is created.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)