Camel Jms[1] provides request/reply implementation, you need to specify the Message Exchange pattern to InOut, and make sure you setup replyTo message header. Using ProducerTemplate[2] in the WS implementation, you can just redirect the request into the JMS queue and handler the response there.
[1]https://camel.apache.org/jms [2]http://camel.apache.org/producertemplate.html -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On January 29, 2015 at 9:41:14 PM, saiya-jin001 (martin.franci...@barclays.com) wrote: > Hi, > as title says, I will have to expose concurrent WS, that would expose > request/response behavior to our legacy system. > This legacy system has a JMS-like access API, meaning when request is > inserted into system, communication ends (ie there is no response to this > request other than return code) and asynchronously via Listeners I can > receive actual response. > This response would need to be paired to original request (still hanging > until timeout happens) and sent back as WS response. > > Since there might be multiple requests at +- same time, there will be a pool > of incoming connections waiting to be served (I would expect accessible via > Camel API somehow). > > I hope I described the topic in understandable way, feel free to ask as much > as necessary. > Can anybody please point me to right direction where to look for > solution/proper approach? > > Thank you > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Exposing-request-response-Web-Service-that-would-interact-with-legacy-system-tp5762229.html > > Sent from the Camel - Users mailing list archive at Nabble.com. >
