thank you, I'll take a look into it
--
View this message in context:
http://camel.465427.n5.nabble.com/Exposing-request-response-Web-Service-that-would-interact-with-legacy-system-tp5762229p5762392.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi,
thank you for your response. I see an issue that legacy API is "JMS like",
not really supporting things like replyTo headers, or queues whatsoever
among other things.
It's more about communication type - request goes one way, and then
asynchronously response comes from another place. I am a bi
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)
