+1 from me, that surely fits into the expectations one would have of a KAR archive.
2011/5/27 Jean-Baptiste Onofré <[email protected]>: > Yes, agree, > > as described in KARAF-675, I also propose to add some properties in > etc/org.apache.karaf.features.cfg to define a kind of autostart policy. > > Regards > JB > > On Fri 27/05/11 11:01 , Andreas Pieber 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: >> >> >> ... >> >> >> 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 >> >> >> >> > > > > -- -- *Achim Nierbeck* Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead
