Hi Aron Yes it's possible but I do agree that the CXF documentation and example we currently have isn't great.
However I am writing a very long tutorial that does part of what you need. Check it out at: http://activemq.apache.org/camel/tutorial-example-reportincident.html when you have very good time, as it's rather long and starts from 0. See also this ticket: http://issues.apache.org/activemq/browse/CAMEL-797 when you can see how you can catch exception and still return a response to the CXF. Med venlig hilsen Claus Ibsen ...................................... Silverbullet Skovsgårdsvænget 21 8362 Hørning Tlf. +45 2962 7576 Web: www.silverbullet.dk -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Aaron Mulder Sent: 3. september 2008 23:33 To: [email protected] Subject: Camel (& CXF?) for Web Services Is there a way to set up Camel to do something like this: - accept an incoming Web Services call - invoke a bean to validate the arguments provided in the SOAP call - if invalid, return an error response to the original Web Services caller - if valid, call Velocity or XSLT or something to transform the SOAP input into another XML format - pass the new XML document as the argument to a remote HTTP service - get the response from the remote HTTP service, transform it, and return that as the response to the original SOAP call I guess my issues are, the Camel-CXF documentation and example aren't real clear to me, and I'm not clear on whether you can set up this whole chain to be IN-OUT so the response from the remote HTTP service can propagate back through additional transformations and be the response for the original SOAP call. I expect it would be easier to have CXF invoke a Spring Bean on the original Web Services call and that bean does all the other work that's described. But I'm wondering if it's possible to set it up as a Camel route instead, which would help decouple all the steps. Thanks, Aaron
