The place where I work one of the other team started using Apache camel in their implementation.
Well our team also wanted to start implementing camel.
I am not comfortable writing business logic in XML's.
I like my code to be more friendly for debugging and easy while implementing.
What's your take on this guys.
Thats true but my colleagues from other team say that the reason why they are using camel is because implementation has became so quick.
Last time they consumed a soap call into their service and it was finished very quickly.
So they have their point but I need some more information on why we should not use it.
nithin chinni wrote:So they have their point but I need some more information on why we should not use it.
Well, my old fart's opinion is that it's part of the general "dumbing down" of software; probably because employers think they will be able to hire a "configurator" for half the price of a programmer.
My opinion: You gets what you pays for.
I can certainly see it's uses for configuring large enterprise systems if you're willing to spend the time and effort to set up a proper DTD; but even then, the syntax rules are pretty basic, and the error messages are absolutely atrocious - even worse than the ones for Java generics (and that's saying something).
Furthermore, in 80% of the cases I've seen, an old-fashioned Properties-style file (for the Unix-minded: config-file) is more than enough, and way easier to follow.
My 2 cents; for what it's worth.
"Leadership is nature's way of removing morons from the productive flow" - Dogbert
Articles by Winston can be found here