I have a camel route that starts with a cxfEndpoint1 (consumer) that works as a CXF server and represents the interface defined in wsdl1. The route is a pass-through route that sends to a backend web service using CXFEndpoint2 (producer) pointing to wsdl2.
The interface for wsdl1 (incoming) is slightly different (different element names, and namespace) than the outgoing wsdl2 interface. We need to introduce transformation in between that transforms message. I'd like a strategy for introducing transformation that is declarative and doesn't force me to write java DOM code or XSLT. I found the CXF transform feature and it looked promising. I'm using it in my route. But i'm having some issues. Is it designed for such a use-case? The problem i have is that the transform seems to occur on entry before the message "hits" CXFEndpoint1. So if I apply the transform feature to the CXFEndpoint1 (listener), and the transform defines namespace or element changes (goal is to conform the message to wsdl2) then I get an exception that the operation name or namespace is incorrect. I'm guessing its because by transforming the message at CXFEndpoint1 at an interceptor that occurs before the message is validated against WSDL1, so it breaks. So i'm coming to the conclusion that the transform feature is not a good way to achieve my goal of a generic all-purpose declarative tranfomration strategy in a camle pass through route from one CXFEndpoint (consumer) to another CXFEndpoint (producer). Can someone deny or confrm my thoughts on this, or recommend an approach to do this type of declarative mapping / tranform simimilar to CXF transform feature that would allow me to accomplish? -- View this message in context: http://cxf.547215.n5.nabble.com/cxf-transform-feature-for-Declarative-transform-in-camel-route-tp5746295.html Sent from the cxf-user mailing list archive at Nabble.com.
