Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: error (athena.apache.org: local policy)
Date: Wed, 4 Feb 2015 07:58:33 -0700 (MST)
From: saiya-jin001 <martin.francisty@barclays.com>
To: users@camel.apache.org
Message-ID: <1423061913581-5762390.post@n5.nabble.com>
In-Reply-To: <etPan.54cf0a6e.74b0dc51.11f@dhcp-128-55.nay.redhat.com>
References: <1422537447070-5762229.post@n5.nabble.com>
 <etPan.54cf0a6e.74b0dc51.11f@dhcp-128-55.nay.redhat.com>
Subject: Re: Exposing request/response Web Service that would interact with
 legacy system
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

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.