You should listen to CamelContext objects being registered as OSGi services.
If they all have autostart = false, you could then manually control them.
On Mon, Jan 23, 2012 at 10:51, kmoens <kris_mo...@yahoo.com> wrote:
> Hi JB,
>
> thanks for the idea. Not sure this covers our needs, we want to control
> automatically the startup of deployed routes at both boottime of karaf and
> deploy time of a new bundle containing routes.
>
> In this case the bean you proposed should be listening on 'deploy events' of
> bundles having routes in spring xml files, how to achieve that?
>
> When I activate trace, I see the follwing messages logged:
>
> 13:41:18,915 | INFO | SpringOsgiExtenderThread-3 |
> OsgiBundleXmlApplicationContext | 47 - org.springframework.context -
> 3.0.5.RELEASE | Refreshing
> OsgiBundleXmlApplicationContext(bundle=com.my.samples.Sample1,
> config=osgibundle:/META-INF/spring/*.xml): startup date [Wed Jan 18 13:41:18
> CET 2012]; root of context hierarchy
> 13:41:18,915 | TRACE | SpringOsgiExtenderThread-3 |
> OsgiBundleResourcePatternResolver | 60 - org.springframework.osgi.io - 1.2.1
> | Found root resources for [osgibundle:/META-INF/spring/] :{URL
> [bundle://138.0:0/META-INF/spring/]}
> 13:41:18,915 | TRACE | SpringOsgiExtenderThread-3 |
> OsgiBundleResourcePatternResolver | 60 - org.springframework.osgi.io - 1.2.1
> | Resolved location pattern [osgibundle:/META-INF/spring/*.xml] to resources
> [URL [bundle://138.0:0/META-INF/spring/Sample1.xml]]
>
> I was wondering if we could find a way to extend the spring deploy process
> some how and add our condition.
>
> BRs,
> Kris
>
>
> --
> View this message in context:
> http://karaf.922171.n3.nabble.com/Karaf-managing-Camel-routes-startup-behavior-tp3669403p3681405.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
--
------------------------
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
FuseSource, Integration everywhere
http://fusesource.com
