Hi Ah that is a little pitfall with the producerTemplate as it has many methods. http://activemq.apache.org/camel/producertemplate.html
You should use sendXXX for IN only message exchange patterns You should use requestXXX for IN-OUT message exchange patterns So you should use requestBody: result = camelProducerTemplate.requestBodyAndHeaders(endPointUri, httpBodyString, exchangeMapHeaders); What is the content on endPointUri? Do you send it the direct or the http endpoint? Med venlig hilsen Claus Ibsen ...................................... Silverbullet Skovsgårdsvænget 21 8362 Hørning Tlf. +45 2962 7576 Web: www.silverbullet.dk -----Original Message----- From: GLD [mailto:[EMAIL PROTECTED] Sent: 7. november 2008 11:28 To: camel-user@activemq.apache.org Subject: How to process the response in Camel Hi all, I want to make a Camel base engine that adapts web services requests and replies For example : - convert currencies from dollars to euro in both requests and responses - The client understands Dollars - The server understands euros. I have the following route <endpoint id="httpEndpointBackend" uri="http://myEuropeanServer.com/myservice"/> <route> <from uri="direct:myServletServiceUri" /> <!-- called by a servlet doGt and doPost methods--> <process ref="myProcessor" /> <to ref="httpEndpointBackend" /> </route> In my servlet, I extract http headers and body, send them to by endpoint using result = camelProducerTemplate.sendBodyAndHeaders(endPointUri, httpBodyString, exchangeMapHeaders); With this configuration, I can successfully process the request but I cannot process the response. I think it because processors are asynchonous but my process is synchronous. Is there a way to either - use processors in a synchronous way (like servlet filters chain) or - define a processor that will be called once the http endpoint receives its http response Thanks Guillaume -- View this message in context: http://www.nabble.com/How-to-process-the-response-in-Camel-tp20378039s22882p20378039.html Sent from the Camel - Users mailing list archive at Nabble.com.