Hi Declan, I agree that the duplicate camel context is probably related to the aries bug.
At a customer we had a similar requirement of running several instances of the same route with different parameters per instance. There I used a normal Java routebuilder but used java properties to parameterize the routes. I then used a separate RouteBuilderFactory that read the configuration and created several instances of the RouteBuilder above and a applied the routes to the camel context. The downside of my aproach was that I was not able to use a ManagedServiceFactory to easily configure the instances using config admin service and I had to restart my whole set of routes to react to config changes. The nice part was that I only needed one camel context which made the startup a lot faster. Overall your setup looks like a better architecture. I will also try this to see if it maybe works on karaf 2.3.1 which includes aries 1.x. Btw. I recently tested my karaf camel tutorial on Karaf 2.3.1 and found that activemq does not fully work there because of another aries issue. The current Talend ESB release should have this already fixed using an upgraded aries version. We hope to have a fully working activemq with karaf 2.3.2. Best regards Christian 2012/9/26 declancox <[email protected]> > Hi All, > I think the issue I describe in this post might have to do with this issue > https://issues.apache.org/jira/browse/ARIES-584, in my karaf 2.2.9 > installation I am using Aries 0.3.2 Blueprint release, apparently fixed in > 1.0. > > Cheers, > Declan > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Using-ManagedServiceFactory-to-dynamically-deploy-routes-tp5719969p5720007.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
