Hi, 

Thanks for your fast and helpful support Claus. It really helped me.

This is the solution you give me by mail... and may help someone else :




Claus Ibsen wrote:
> 
> You route looks like something like this
> 
> from("direct:acServletServiceBusinessUri?exchangePattern=InOut")
> .to("xslt:transformPricingService.xsl")
> .to("http://localhost:8088/mockPricingSOAP";)
> .to("xslt:transformPricingService.xsl")
> 
> Where the .xsl file is located on the classpath. You can use Spring
> scheme to locate it on the file system instead
> 
> .to("xslt:file://transformPricingService.xsl")
> 
> 
> Where the 2nd xslt transformation might need another file to transform
> the reponse as you want it. However XSLT tends to get complex and hard
> to try and debug. Definitely not a favorite of mine.
> 
> BTW: Camel 1.5.0 has been released. You should consider if possible to
> upgrade.
> 
> 
> So you are nearly there in your route in your spring XML file. You
> need the last xslt processing step. So you need to add a <process
> ref="acXsltProcessor"/> after the HTTP call to SoapUI
> 
> 
>               <route>
>                       <from 
> uri="direct:acServletServiceBusinessUri?exchangePattern=InOut" />
> 
>                       <process ref="acXsltProcessor" />
> 
>       <!--  preprocessor that specify the POST method in Exchange
> header-->
>       <process ref="acHttpPreProcessor" />
>       <to ref="httpEndpointBackend" />
> 
> <!-- INSERT HERE THE LAST XSLT TRANSFORMATION -->
> <process ref="acXsltProcessor"/>
> <!-- Maybe you need another xsl file to convert it back but you could
> then just ref another processor: myOtherXsltProcessor
> 
>               </route>
> 
> /Claus
> 
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/How-to-process-the-response-in-Camel-tp20378039s22882p20476717.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to