Hi,
If you are not a big fan of Spring, you can get full of the control of
the route with the Java DSL.
In most case, the Spring DSL can do the same thing as Java DSL does.
But if you have some customer configuration to set it should be better
to use Java DSL.
BTW, we support to use Guice instead of Spring to do the DI work, and
it's also friendly with the Java DSL.
Willem
srinidandi wrote:
Hi,
Thank you so much for the reply. Will surely try out this.
Just a question.. how does Java dsl fare compared to spring dsl in terms of
ease of development, feature set and maintenance for medium to complex
projects. In short, in my situation, which one will be better to use.
Thanks.
willem.jiang wrote:
Hi,
The Spring Main class support to start with multiple ApplicationContext.
you can pass the ApplicationContext files into it, or use <imports> to
put all the modules routes together.
But you may not share a single camel context within these routes.
Willem
srinidandi wrote:
Hi,
I am new to Camel and I am working on a new application that has multiple
independent modules. Each module has a workflow and there should be an
ability to start multiple modules / workflows in a single jvm instance.
In the above scenarion, if I use camel dsl, each module will have its own
camel context xml which will have the routes defined and a spring main
class
to start a module in its own jvm instance. But how can the ability to
start
multiple modules in a single jvm instance be provided using a single main
launcher class?
Please help.
