[
https://issues.apache.org/jira/browse/QPIDJMS-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy resolved QPIDJMS-371.
--------------------------------
Resolution: Invalid
Closing the Jira as invalid. I did not realized that JMSMapping specification
had already defined the prefixes for the ids.
> String representation of JMSMessageID values generated with message ID policy
> of type 'UUID' cannot be used in selector expressions
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: QPIDJMS-371
> URL: https://issues.apache.org/jira/browse/QPIDJMS-371
> Project: Qpid JMS
> Issue Type: Bug
> Reporter: Alex Rudyy
> Priority: Major
>
> Message ID policy of type {{UUID}} generates {{JMSMessageID}} values of AMQP
> type {{UUID}}. Such {{JMSMessageID}} values represented as {{String}}
> values (returned from method {{Message#getJMSMessageID()}}) in format
> {{ID:AMQP_UUID:<uuid string representation>}}. When such string value is used
> to build a JMS selector expression for example, {{String.format("JMSMessageID
> ='%s'", message#getJMSMessageID() )}}, the expression is sent to the broker
> in unmodified form. The Broker might not be aware about prefix
> ''ID:AMQP_UUID:' and can fail to find the message corresponding the
> expression.
> I did not test other Message ID policies and I guess that similar issue might
> happen for them as well.
> I am not sure whether custom prefixes are added by design with an intention
> to document them as part of JMSMapping specification. If not, it would be
> desirable to strip custom prefixes either from selector expression or
> {{String}} representation of JMSMessageID values.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
