I actually avoid the Camel Processors as I find them unnecessary and they couple your Java to the Camel API. I'll use endpoint injection into a wrapper class and then use the methods on that wrapper class to make calls to the routes. Camel will automatically select the right method on a bean to call in most cases but I usually use the <bean ref="foo" method="bar"/> form in XML to make it a bit more obvious and readable as to what is going on.
On Fri, Apr 29, 2016 at 3:04 AM, NikheelRanjan <nikheel.ran...@gmail.com> wrote: > I also have good amount of experience in IT and I am using camel for more > than 4 years, I also recommend xml and blueprint as the standard.As far as > complexity is concerned,Routes placed in JAVA DSL will not help rather use > of camel processors/beans will help in between to handle the complexity in > a > better way. > Please give ur thoughts on if any body see xml DSL plus use of camel > processors in between to handle complex tasks as a challenge in handling > big > applications and do you think that JAVA DSL has any advantage over it? > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Blueprint-Spring-DSL-vs-JAVA-DSL-tp5781807p5781956.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
