Hi Guillaume, currently, if you drop a features descriptor ino the deploy folder, the features are present, but not installed and the bundles are not started.
So the users have to install the features by hand after. More over, it's the same behavior with a KAR: no features in the KAR are installed/started. On the other hand, it could have sense to have features installed/started automatically when adding the features URL. For instance, adding the Camel features descriptor URL could automatically install/start camel-core, camel-spring and camel-blueprint features. Regards JB On Fri 27/05/11 11:08 , Guillaume Nodet wrote:: What would be the effect ? installing the feature or starting the bundles, or both ? I think dropping a feature descriptor in the deploy folder should automatically install the feature (and start the bundles), I'm not sure to see what the benefit of not doing that would be. On Fri, May 27, 2011 at 10:54, Jean-Baptiste Onofré [email protected]> wrote: > Hi all, > > What do you think about adding an autostart attribute on the features element > ? > > The purpose is to be able to have something like: > > > ... > > > When an user register a features descriptor (using features:addurl), deploy a > KAR containing a features descriptor or drop a features descriptor in the > deploy folder, Karaf will try to automatically start the features with > autostart flag set to true. > > It will avoid users to: > - start by hand features contained in a KAR: the user can drop the KAR into > the deploy folder, but he must connect to Karaf and start the features by hand > - start by hand features after an addurl when the user "controls" the > features content > > Thoughts ? > > Regards > JB > > > > -- ------------------------ Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
