You should use blueprint in the namespace for <routeContext> On Tue, Jul 28, 2015 at 5:07 PM, gersid <[email protected]> wrote: > Found the following issue > when the standard example "camel-blueprint" is modified as following. > > Used the file blueprint.xml with the <camelContext> section replaced with > the following: > > <camelContext xmlns="http://camel.apache.org/schema/blueprint";> > > <routeContextRef ref="myRoutes"/> > </camelContext> > > > <routeContext id="myRoutes" xmlns="http://camel.apache.org/schema/spring"; >> > <route> > <from uri="timer://myTimer?fixedRate=true&period=2000" /> > <bean ref="myTransform" method="transform"/> > <to uri="log:ExampleRouterBlueprint" /> > </route> > </routeContext> > > Such a blueprint hang when starting camel context in local Eclipse > environment. > Or it get in "GracePeriod" oncethe modified example is deployed to Karaf. > (Standard unmodified example is working good in both my evironments) > > And even if I added a reference to emptry <routeContext/> into working > camelContext - it would usually result in hang the camel. > > Camel version used - 2.15.2 > I did not try in Spring or with Java/DSL. > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/blueprint-routeContext-tag-prevents-Camel-from-starting-tp5770023.html > Sent from the Camel - Users mailing list archive at Nabble.com.
-- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2nd edition: http://www.manning.com/ibsen2
