See http://camel.apache.org/loading-routes-from-xml-files.html for loading XML routes at runtime.
For #1 consider using the DSL route creation. It returns Java objects for each of the constituent parts. The DSL does not have to be as 1 contiguous block so conditional logic can be applied to modify it at route creation time at startup. The question of whether to put them into the same context is probably more of a question on what the hardcoded routes represent versus the XML based routes. Are there 2 separate business concepts being expressed or one? As with any design decision like this, opinions will vary. On Mon, May 29, 2017 at 8:55 AM, MaFo <effisucki1...@yahoo.com> wrote: > Hi > > I got the task to build an Event-Dispatching application and decided to use > camel as base framework. > Among others, I have the following requirements: > > 1) Some routes are hardcoded in the software, but the user can configure > some aspects of the route via a web gui (e.g. the condition for a > switch-block or the name of a field to look for). > 2) All other routes are not known at design time, the will be specified by > the customer AFTER the software has been delivered. Therefore the > application should be able to load routes from XML files and/or from JAR > files (via routebuilders or similar) > > So I have to collect routes from 3 sources: XML, JAR files and dynamically > build by JAVA DSL with input from webgui. > > How can I build my application so all those routes come together in one > context and can be monitored, e.g. with HAWT.IO? > Is it even recommended to put all those routes in the same context? > > Thanks for your help! > > > > -- > View this message in context: http://camel.465427.n5.nabble. > com/Need-advice-on-application-architecture-with-camel-tp5801290.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- ------------------------------------------- Craig Taylor ctalk...@ctalkobt.net
