The InOut pattern contains the request and the exchange. When a provider receives an InOut exchange, it has to fill the "out" message and send the exchange back. The NMR will route the exchange the the consumer component (the one who created the exchange). In this case, the http consumer endpoint will create an InOut exchange when receiving an HTTP request, will send it to the http provider endpoint. The http provider endpoint will send an HTTP request to the external web service, and when the http response comes, will create the out message and send it back to the http consumer (who will fill the HTTP response for the client).
On 8/13/06, Bernard Lupin <[EMAIL PROTECTED]> wrote:
I've read all the posts "How to call a external webservice" (http://www.nabble.com/forum/ViewPost.jtp?post=5464647&framed=y) and have not found an answer to the problem I have : In this configuration with servicemix-http and 2 http endpoints client -> http endpoint consumer -> http endpoint provider -> external web service, the message is well treated by the external WS but never returned to the client. Is it a bug or a config problem ? More generally speaking, I don't understand how routing works after the chain below : how servicemix knows that the answered message should go from http endpoint provider to http endpoint consumer and then to the client ? I've read some posts about In messages or InOut messages. Where can I configure such information ? Thanks a lot. Bernard -- View this message in context: http://www.nabble.com/routing-with-servicemix-http-tf2097218.html#a5780622 Sent from the ServiceMix - User forum at Nabble.com.
-- Cheers, Guillaume Nodet
