Am 25.01.2012 14:58, schrieb Claus Ibsen:
It is *not* trivial for people getting started with Camel to figure
out how to use a Spring XML file for the regular Spring stuff.
And then how to add Camel in there, and use the Java DSL.
As you need to add<package>com.foo</package> or use a
<routeBuilderRef> etc. to link the Spring XML file to the Java
RouteBuilder.
There are two kind of people getting started with Camel.
1) People who would avoid Java code and do as much in XML
2) People wo are more savy coders and want to use Java code, but
Spring XML for their bean configuration.
If you have a single archetype for 1+2 then it *confuses people*.
What I meant is that it is easy to add a camel route to a spring config
when the camel context is already defined as a bean.
So if people have an archetype that uses a camel context in spring and a
Java route builder then adding an xml route
is easy and removing the a java route builder is also easy. We could
even define a route in java and another in xml to show both cases
in the same archetype.
In my experience it is much easier for people to delete unneeded parts
than adding new parts. So that could work.
Christian
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
