[
https://issues.apache.org/jira/browse/QPIDJMS-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16411850#comment-16411850
]
Robbie Gemmell commented on QPIDJMS-371:
----------------------------------------
The prefixing going on is per behaviour already in the AMQP JMS mapping doc,
and needed support the different AMQP types round tripping through the
application layer for use as correlation-id etc of the same underlying type.
Per Rob's comment, this might actually be an area for the mappings (rather than
clients) selector behaviour. JMS doesnt define how select a Binary or ulong or
UUID since it doesnt have them. Essentially if you want it to behave per JMS
espectation with ease though, stick to the default strings.
I know you are trying this because of the 1.0 -> 0-10 conversion discussion on
the list right now from use of the two clients. In that scenario, really the
broker should probably be allowing the 0-10 consumers to select the message
with the ID it has generated for them during converstion, rather than say
having the other clients change to send actual AMQP UUIDs.
> 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]
