Hello Willem, Thanks for the reply. I was playing around with this stuff and tried some minor changes to the CXFConsumer and CXFInvoker to deal with the WebServiceProvider annotation and work accordingly. I could get it to work and have some thoughts on this. Since WebServiceProvider is the JAX-WS standard way of dealing with message/payload directly, couldn't we make the WebServiceProvider endpoint the default way of dealing with Message/Payload mode. So a camel CXFEndpoint that needs to receive the data in message/payload mode would just have to declare a SEI with @WebServiceProvider annotation and the camel route would be invoked with the specified format . From camel side, this would mean that we would let CXF do all the message construction job and finally call the CamleInvoker for dispatching to the camel route using the modified CamelInvoker. I am sending you a patch file with the changes I made, please have a look and let me know what you think.
Aswin -- View this message in context: http://www.nabble.com/Camel-CXF-Spring-Tomcat-configuration-tp15350144s22882p15417089.html Sent from the Camel - Users mailing list archive at Nabble.com.
