Yeah, there are a bunch of things that need to be done to enhance the features descriptors. In addition to the start level, an attribute specifying if the bundle should be started or not could be useful in case you don't want some bundles to be started automatically. I have also plans to leverage OBR repository inside features that i'll discuss at some point.
On Tue, Jun 29, 2010 at 10:15, Charles Moulliard <[email protected]> wrote: > Hi, > > The existing Karaf platform uses two mechanism to deploy and start > bundles at the launch of the Karaf server. Thes first one uses the > bundles listed in the startup.properties file (+ bundle level) while > the other is the provisioning mechanism based on feature file. > > It is possible to deploy "project" bundles at the startup of the Karaf > but that means that they should be present in the default system > repository (and listed in startup.properties file). To use another > repository, the variable bundle.loacations must be set in the file > config.properties. > > Personally, i think that the start up mechanism should be keep for the > launch of Karaf and should not be used to start project bundles. They > should be deployed and started through features mechanism > > Nevertheless, feature xml file does not define the bundle startup > level. So I suggest that we add a new attribute to the description of > the bundle/feature to define the bundle level ? > > What do you think about that ? > > KR, > > Charles Moulliard > > Senior Enterprise Architect (J2EE, .NET, SOA) > Apache Camel - ServiceMix Committer > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Blog : http://cmoulliard.blogspot.com | Twitter : > http://twitter.com/cmoulliard > Linkedin : http://www.linkedin.com/in/charlesmoulliard | Skype: cmoulliard > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
