Well, I'm not completely sure about marking a feature as installed as soon as the bundles are all installed, neither the opposite actually.
There is some work going on in the OSGi Alliance about multiple frameworks in one JVM (see http://www.osgi.org/Download/File?url=/download/osgi-core-4.3-early-draft1.pdf for more informations). This would enable to have a tree of OSGi frameworks instead of a single instance and would enable controlled sharing between a framework and its parent. This would enable a controlled level of isolation and could be used to make sure some features don't interfere with each other. That's one of the reason i'm not totally convinced about your proposal. If we'd were to use nested frameworks, each feature would have its own framework, so that would not map well to your proposal. The two other things i have in mind for features are: * give a lifecycle to a feature (start / stop) * allow more control on the bundles when installed (started level, start state) * leverage obr to compute a transitive closure of the feature before installation The last one would allow a more loose definition of a feature but just specifying the list of key bundles and let the features service determine all the required dependencies and download / install them. FWIW, nested frameworks are not available yet in felix (there's only a prototype in an equinox branch), so we can't really use those now, but the other things should be possible to implement now. In particular, the use of OBR should now be possible since the new release as some acceptable performances. On Thu, May 20, 2010 at 16:39, Lukasz Dywicki <[email protected]> wrote: > > Hello, > I would talk about Karaf Features. At this moment features can be used to > install or uninstall set of bundles but FeaturesService does not track state > of bundles. > > For example when we install servicemix-saxon feature and after that remove > saxon bundle feature state is installed but feature is not complete. When we > install bundles from some feature by hand feature should be also marked as > installed. > These two things will make Karaf Features better. :-) What do you think? > > Regards, > Lukasz > -- > View this message in context: > http://old.nabble.com/Karaf-features-improvements-tp28622180p28622180.html > Sent from the Apache Felix - Dev mailing list archive at Nabble.com. > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
