Release 0.9

Hi all, Do you know when the qpid-proon 0.9 lib would be release? The initial plan was be at the end of the year (2014), just to know! Regards -- View this message in context: http://qpid.2158936.n2.nabble.com/Release-0-9-tp7618431.html Sent from the Apache Qpid Proton mailing list archive

Filtering message bugged?

Hi all, Scenario: Creation a filter to recieve any message containing the filter. pn_link_t* link = pn_messenger_get_link(msgConsumer, (myQueue, false); pn_messenger_subscribe(msgConsumer, (myQueue); link = pn_messenger_get_link(msgConsumer, myQueue, false); pn_link_open(link); // We create the

RE: CorrelationId

Hi, Any body have an idea about this? The new version of the lib will fix this, or it's my code? regards -- View this message in context: http://qpid.2158936.n2.nabble.com/CorrelationId-tp7614606p7617531.html Sent from the Apache Qpid Proton mailing list archive at Nabble.com.

Next realease of qpid-proton

Hi all, Do you where can I find the roadmap for qpid-proton library? Regards -- View this message in context: http://qpid.2158936.n2.nabble.com/Next-realease-of-qpid-proton-tp7617393.html Sent from the Apache Qpid Proton mailing list archive at Nabble.com.

Re: Next realease of qpid-proton

Thank you Rafael -- View this message in context: http://qpid.2158936.n2.nabble.com/Next-realease-of-qpid-proton-tp7617393p7617395.html Sent from the Apache Qpid Proton mailing list archive at Nabble.com.

Re: CorrelationId

Hi Dominic, I set PN_TRACE_FRM=1 and here my trace. [006FC110]: - SASL [006FC110]:0 - @sasl-init(65) [mechanism=:PLAIN, initial-response=b\x00emc2\x00emc2] [006FC110]: - SASL [006FC110]:0 - @sasl-mechanisms(64) [sasl-server-mechanisms=@PN_SYMBOL[:ANONYMOUS, :PLAIN]] [006FC110]:0 -

RE: CorrelationId

Here the right code //Doing this one time pn_messenger_t* msgConsumer= pn_messenger(NULL); pn_messenger_set_timeout (msgConsumer, 1000); pn_messenger_set_blocking (msgConsumer, true); pn_messenger_set_incoming_window (msgConsumer, 1); // Doing this more time pn_link_t* link;

RE: CorrelationId

, Xavier Subject: Re: CorrelationId Hi Xavier, so 006FE360 is your messenger that is responsible for subscribing and receiving the messages based upon the selector. xavier wrote [006FE360]: - SASL [006FE360]:0 - @sasl-init(65) [mechanism=:PLAIN, initial-response=b\x00emc2\x00emc2] [006FE360

Re: CorrelationId

Hi Dominic unfortunately, it 's does not work!! I try your idea, see my code (I move the pn_link_detach() and pn_link_open() in all my code, but .) Here my code: // Init one time to use many time pn_messenger_t* msgConsumer= pn_messenger(NULL); pn_messenger_set_timeout (msgConsumer, 1000);

Re: CorrelationId

Hi all, I found the solution (for ActiveMq, with a connector in AMQP, and a connector with openwire), so I share the solution. I used the idea of Dominic Evans, so If I want to get a message from a filter (for example correlationId ), I did this: pn_messenger_t* msgConsumer= pn_messenger(NULL);

Re: CorrelationId

Hi all, I re start to work on this issue!!! and it is not work! So here my last code: // get recv link pn_link_t* link = pn_messenger_get_link (messengerConsumer, myAdress, false); // get the source link, is't it, I saw, before doing that on the the activemq's log, than the filter is: the

Re: CorrelationId

Hi all, pn_messenger_get_link is not in the 0.7 qpid lib, right? Is it in the next release 0.8 ? If yes do you have any date for it, and code sample, with? Thanks a lot regards -- View this message in context: http://qpid.2158936.n2.nabble.com/CorrelationId-tp7614606p7614826.html Sent

Re: CorrelationId

Hi Frase, Thanks for your explanation, but here, my code: In the requester: char * corrId; . . pn_bytes_t bytes = pn_bytes(correlationId.size(), corrId); pn_atom_t id; id.type = PN_STRING; id.u.as_bytes = bytes; pn_message_set_correlation_id(message, id); and after, send it

Re: CorrelationId

Hi all, Thanks you for your reply, help? So if I understand properly, to do that with messenger is not trivial??? But I don't understand why, because with the pattern request/reply in asynchronous mode, and with dedicated queue, we must have this feature. isn't it? So to do that must I take some

CorrelationId

Hi all, I am new with Qpid Proton So I try to using it with ActiveMq, and migrate my old code based on CMS (JMS for C) ! I would like to get a message filtered on correlationId, like with CMS: session-createConsumer(destination, JMSCorrelationID=' + correlationId + ') But with Qpid proton