I ran into a similar issue with system bundles being partially started with Apache ODE and related startup issues. It was my suggestion then to start system bundles < 60 and user bundles >60. Would this apply to all bundles that are supplied with features on SMX (like ODE), or just select ones? I'm highly in favor of this, btw.
>>> Freeman Fang <[email protected]> 1/10/2011 4:32 AM >>> Hi, How about we specify start level for camel feature bundles less than 60, so that when restart servicemix, the camel related bundles always get started before end users bundle, this can avoid lots of asyn issues customer may encounter, such as camel component not available yet when end users bundle get started. Actually this discussion initially from fuse forum[1], and I'm not very sure heavily depend on bundle start level is a good practice in OSGi world, but I must admit that in servicemix camel should be considered as a part of the framework, so give higher priority for camel bundles seems OK. Btw, karaf features already support specify start level, so it should be doable in Servicemix to do it. I'd like hear more voice, thoughts? [1]http://fusesource.com/forums/thread.jspa?threadID=2493 TIA Freeman -- Freeman Fang ------------------------ FuseSource: http://fusesource.com blog: http://freemanfang.blogspot.com twitter: http://twitter.com/freemanfang Apache Servicemix:http://servicemix.apache.org Apache Cxf: http://cxf.apache.org Apache Karaf: http://karaf.apache.org Apache Felix: http://felix.apache.org
