> As I say selectors are 'coming soon', there is a patch for XSLT based
> selectors attached to QPID-530[1] if you are interested in previewing that.
Out of curiosity, why XSLT? Is it to handle message body selection as
well as the more traditional headers?
How fast is it?
Selectors by correlati
Cullen Davis wrote:
I followed your lead and modified the tests to pass a protocol into the Connection::open. When the ConnectionImpl object was instantiated, the ProtocolRegistry().find(proto) failed with an "Unknown Protocol" error. I was using "ssl" as the target protocol.
Any additional
I followed your lead and modified the tests to pass a protocol into the
Connection::open. When the ConnectionImpl object was instantiated, the
ProtocolRegistry().find(proto) failed with an "Unknown Protocol" error. I was
using "ssl" as the target protocol.
Any additional thoughts?
Cullen J
When it's committed, let me know if I can help with testing.
//Bill
On 08/14/2009 10:24 AM, Gordon Sim wrote:
Bill Whiting wrote:
Gordon,
Is the patch to add the XSLT based selectors included in the current
trunk for SVN?
Not yet, no.
---
Bill Whiting wrote:
Gordon,
Is the patch to add the XSLT based selectors included in the current
trunk for SVN?
Not yet, no.
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mai
Gordon,
Is the patch to add the XSLT based selectors included in the current
trunk for SVN?
//Bill
On 08/14/2009 09:11 AM, Gordon Sim wrote:
Bill Whiting wrote:
So the only way to receive a specific message by the correlationId
(at this time) would be to browse the queue looking for the corr
Bill Whiting wrote:
So the only way to receive a specific message by the correlationId (at
this time) would be to browse the queue looking for the correct message?
Thats right.
As I say selectors are 'coming soon', there is a patch for XSLT based
selectors attached to QPID-530[1] if you are i
Ah, sorry Bill - then I think Gordon's reply was the most apposite !
M
On Fri, Aug 14, 2009 at 1:38 PM, Bill Whiting wrote:
> Thanks for the quick reply Marnie,
> My application is written in C++, so I don't think that helps.
>
> //Bill
>
>
> On 08/14/2009 05:15 AM, Marnie McCormack wrote:
>
>>
Hi Bill,
You can use JMS message selectors to get the message you want from the
queue/topic, you specify the selector string on the creation of the consumer
(via the Session) e.g.
session.createConsumer(queue,"JMSCorrelationID="+correlationID)
Hth,
Marnie
On Fri, Aug 14, 2009 at 1:23 PM, Bill
Thanks for the quick reply Marnie,
My application is written in C++, so I don't think that helps.
//Bill
On 08/14/2009 05:15 AM, Marnie McCormack wrote:
Hi Bill,
The Java Broker/Client support JMSCorrelationId& JMSMessageId. They
are exposed as part of the properties on the JMSMessage, allowi
So the only way to receive a specific message by the correlationId (at
this time) would be to browse the queue looking for the correct message?
//Bill
On 08/14/2009 02:58 AM, Gordon Sim wrote:
Bill Whiting wrote:
Is there a sample program or documentation that shows getting a
message from a q
Hi Bill,
The Java Broker/Client support JMSCorrelationId & JMSMessageId. They
are exposed as part of the properties on the JMSMessage, allowing bridging
across applications and messaging services.
In the Java example package, the simple.reqresp classes contain code showing
how to get/set the JMSC
Cullen Davis wrote:
I have two questions regarding SSL and the C++ broker / C++ client running
qpidd (qpidc) version 0.5 from a trunk build.
1) Start c++ qpid broker as follows
qpidd --log-enable debug:ssl --log-source yes \
--log-function yes \
--auth no \
--load-module sr
13 matches
Mail list logo
