+1 On Fri, May 27, 2011 at 12:01 PM, Andreas Pieber <[email protected]> wrote:
> BIG +1. This would make some installation issues much easier. E.g. > pointing a customer to the "ueberfeature" and with a simple addUrl (he > can paste into his console) everything is installed. Nevertheless, one > think we should keep in mind here: If we allow autostart of features > there should be a configuration in Karaf to suppress autostart (for > e.g. security reasons) either completely or via a white-list. E.g. all > features loaded from org.mycompany.* should autostart, all others not. > > Kind regards, > Andreas > > On Fri, May 27, 2011 at 10:54 AM, 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: > > > > <feature name="myfeature" version="1.0-SNAPSHOT" autostart="true"> > > ... > > </feature> > > > > 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 > > > > > > > > > -- *Ioannis Canellos* * http://iocanel.blogspot.com Apache Karaf <http://karaf.apache.org/> Committer & PMC Apache ServiceMix <http://servicemix.apache.org/> Committer *
