You can use two normal (non-temporary) queues, one for requests and one for responses. Each request will have a correlation-id header. Let's call the requesting service A and the responding service B. Service A will send to /queue/requests. Service B will receive (consume) the request, and send the response to /queue/responses. The response that Service B sends will have a correlation-id that matches the request. Service A can then subscribe to /queue/responses with a selector (http://activemq.apache.org/selectors.html) that matches the correlation-id. Therefore, Service A will only consume the response that matches the correlation-id of the request.
JLuna ----- Original Message ---- > From: Alexander L. <ferve...@yandex.ru> > To: users@activemq.apache.org > Sent: Tuesday, August 11, 2009 4:56:36 AM > Subject: Implement request response with JMS over Stomp > > > Hello All, > > Article > http://activemq.apache.org/how-should-i-implement-request-response-with-jms.html > How should I implement request response with JMS describes how to implement > request response using temporary queues created by clients. > > Stomp does not support temporary queues > http://activemq.apache.org/cms/stomp-support.html ActiveMQ-CPP Stomp Support > , thus such scheme is not applicable right as it described . > > What could be alternate scheme for request-response with JMS over Stomp? > > Thanks. > -- > View this message in context: > http://www.nabble.com/Implement-request-response-with-JMS-over-Stomp-tp24914033p24914033.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
