On 06/26/2013 02:03 PM, Robbie Gemmell wrote:
On 26 June 2013 13:16, Gordon Sim <[email protected]> wrote:
From 0.22 you can specify a selector in the link directly, e.g.
Receiver r = createReceiver("my-queue;
{link:{x-subscribe:{arguments:{x-filter-jms-selector:\"colour in ('red',
'blue')\"}}}}");
Sorry! What I meant to write there was:
Receiver r = createReceiver("my-queue; {link:{selector:\"colour in
('red', 'blue')\"}}");
Can you clarify what you mean above? Are you saying the client will map
'x-filter-jms-selector' from the address string into 'x-apache-selector' in
the actual 0-10 subscribe command? Or was the second example meant to be
more different?
It was indeed meant to be different. I do apologise for the error and
the confusion it caused.
Either way, if the 0-10 subscribe argument were 'x-apache-selector' it wont
currently be picked up by the Java broker as it doesn't check for that
particular argument, only its 'historic x-filter-jms-selector'
Right. Over 0-10 I think the former is the only valid approach for using
the Java broker's selector.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
