Hi Richard, Thanks for your comment. I agree with your argument however i can very easily implement a custom processor and use it for multiple routes. A component internally calls a processor in the form of Consumer/Producer attached to an endpoint.
So again if i look at the XSLT component i feel that a custom processor would have done that as well and could have been reused. So you already have XsltBuilder (processor) which is directly used from inside the xslt component. Apart from using that processor it does nothing much. So that raises the question again in my head as to when to create a component and when not to. Best Regards, Madhav Richard Kettelerij wrote: > > I've discussed the choice between components and processors earlier in > http://camel.465427.n5.nabble.com/How-to-handle-firefox-outputting-files-as-component-td3047751.html#a3047804 > (second message). > -- View this message in context: http://camel.465427.n5.nabble.com/Custom-component-Vs-Custom-processor-tp3256585p3258487.html Sent from the Camel - Users mailing list archive at Nabble.com.
