Not dead yet. I've got a round-trip request/response over a jms transport working using the "temp reply queue per request" anti-pattern. I need to do something like suggested below in the email with correlation ids to avoid this. Not sure why activeMQ suggests setting the correlationID of the response to the correlationId of the request (seems odd: http://activemq.apache.org/how-should-i-implement-request-response-with-jms.html)
Post if you want some not-ready-for-production code. -----Original Message----- From: Jochen Wiedmann [mailto:[EMAIL PROTECTED] Sent: Mon 7/23/2007 4:22 PM To: xmlrpc-dev@ws.apache.org Subject: Re: JMS transport for XML-RPC On 7/23/07, Petersen, Jennifer <[EMAIL PROTECTED]> wrote: > You can work syncronously with JMS with the blocking receive() message > and selector where correlationIdOfReply=requestMessageId. Nice! That would indeed make the transport as simple as the various HTTP transports. In fact, it might even be much smaller, as it doesn't waste energy for headers and stuff like that. -- "Besides, manipulating elections is under penalty of law, resulting in a preventative effect against manipulating elections. The german government justifying the use of electronic voting machines and obviously believing that we don't need a police, because all illegal actions are forbidden. http://dip.bundestag.de/btd/16/051/1605194.pdf --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
