On Wed, Nov 10, 2010 at 12:24 PM, unmarshall <[email protected]> wrote: > > 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. >
A component allows you to abstract at a higher level and you can use endpoints to leverage the component. So you can just send the message to an endpoint with an URI String. A custom processor you cannot do this. In the end user what suits you best :) > 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. > -- Claus Ibsen ----------------- FuseSource Email: [email protected] Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
