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 bit worried that I will have to implement this behavior manually, ie listener callback with response being propagated back to request. Having multiple thread scenario adds a bit of complexity on top of that. Or is there any way of reusing already-existing Camel functionality (or other frameworks like Spring)? Thank oyu
-- View this message in context: http://camel.465427.n5.nabble.com/Exposing-request-response-Web-Service-that-would-interact-with-legacy-system-tp5762229p5762390.html Sent from the Camel - Users mailing list archive at Nabble.com.
