Hi Good ideas. There is a JIRA ticket about improving <routeContext> in a future Camel release. You are welcome to put your ideas on that ticket, so we take these into consideration.
On Mon, Jan 20, 2014 at 8:22 AM, Sven Nold <[email protected]> wrote: > Hi, > > I really like the feature of <routeContext>, but I think some features are > missing. Maybe someone could point me to the right direction. > > - routeContext must not be empty > I would like to give users (other developers) the possibility to extend/add > their own routes. But currently the routeContext must be filled with at least > one dummy route. > > - routeBuilder (ref) not supported > There is no way to use routeBuilder ref for Java DSL routes. Here is the > fallback to use camel vm component, but it would be much nicer if I could use > the same syntax as in camelContext. > > - routeContextRef not supported > Extension of other users (developers) in XML can get quite fast very large. > Currently there is no way to externalize those routes :( > > Please let me know your thoughts how to either make use of current available > components/features to accommodate the above needs. > > Best regards, -- Claus Ibsen ----------------- Red Hat, Inc. Email: [email protected] Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen Make your Camel applications look hawt, try: http://hawt.io
