I'm not sure what kind of processing you are doing, but if you can setup right message header (operation name) and message body, you should have no trouble to invoke the service. Maybe you can show us, you want prepare the SOAP message for invocation.
-- Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat.com Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English) http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Saturday, January 5, 2013 at 6:51 PM, helander wrote: > I am using camel-cxf for calling a web service. I am using a producer > template to create an exchange that has an in message that "contains" the > web service call details (input parameters as POJOs, operation name, ). The > exchange is sent to a route that looks as: > > from("direct:xyz").to("cxf:http://......";); > > This works very well and the service is properly called, but what if I > wanted to do some processing in the route of the generated SOAP messages and > not having the service called, how would I do then? > > Thanks > > Lars > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Producing-consuming-SOAP-messages-to-from-POJOs-using-camel-cxf-tp5724949.html > Sent from the Camel - Users mailing list archive at Nabble.com > (http://Nabble.com).
