I don't know how to do this exactly, but what the maven goal does is to start Spring Context, that starts Camel Context, and then process the routes built by the XML configuration file. If you do something through Spring, to load the routes written in Java, you can achieve the same thing.
For your organization, I believe it depends on your design. Specific RouteBuilders for specific routes. Global RouteBuilders for macro routes that interconnect those specific routes. Anyway, the good thing of DSL in Java/Scala is that you can design the way you think is more appropriate, though in XML the same can be done. Cheers, Bruno Borges blog.brunoborges.com.br +55 21 76727099 "The glory of great men should always be measured by the means they have used to acquire it." - Francois de La Rochefoucauld On Tue, Oct 6, 2009 at 9:51 AM, uprooter <uproo...@gmail.com> wrote: > > Hello. > I have some thoughts on how to design my camel based application. > Basically it has to do JMS mediation most of the time, I want to stick to > java code rather than XML configuration so I have a bunch of routes written > in java DSL. > > Right now I have one or two RouteBuilders, each holding a bunch of routes. > but it's not comfortable to work with as the IDE(netbeans in that case) > cannot distinguish between routes. > Is there another way to split the routes into classes or have some other > way > to make things more organized for the human reader ? > > PS I tried to create a graph using camel-dot however it doesn't seems to > work with java DSL. > > -- > View this message in context: > http://www.nabble.com/human-friendliness-of-camel-tp25768104p25768104.html > Sent from the Camel - Users mailing list archive at Nabble.com. > >
