I have a camel route that routes from a Camel CXF (producer) Endpoint, performs some transformation, then the route sends to a CXF (consumer) Endpoint. I've tried options like XSLT, xquery, and velocity, for performing the transformation step - but the developers I'm working with would prefer a declarative approach where the transformation mapping can be expressed in Spring. We want to do a few things like change an element name, append an element, change namespace, etc. I had a look at the CXF-specific transformation feature. http://cxf.apache.org/docs/transformationfeature.html The concept is great because it allows you to express a simple transformation using a expression language "mapping" right there in the Spring XML. But this feature I found to be too tightly tied to the CXF endpoint and got into trouble with things blowing up when the message didn't exactly adhere to WSDL. Seems like a Camel component that could be placed in any arbitrary location within a route and could be expressed using a similar mapping as the CXF transformation feature would be a valuable thing to have in CAmel. Does anyone know if such a camel component exist that allows for this type of Spring-based transformation mapping language? I wonder if we could reuse whatever underlying code from the CXF transformation feature to a camel component to do the same?
-- View this message in context: http://camel.465427.n5.nabble.com/transform-component-tp5754270.html Sent from the Camel - Users mailing list archive at Nabble.com.