I think Filippo's suggestion about the features command would help a bit. Bundles are somewhat low levels things that end users, administrators or deployers should not have to deal with too much. We should enhance the features command to provide this high level view of what's inside Karaf.
On Wed, Oct 21, 2009 at 14:20, David Bosschaert <[email protected]> wrote: > I actually agree with Jeremias and Filippo as well that for deployment > multiple bundles is definitely better. However my experience is also that > people new to OSGi are sometimes hesitant to get started with something if > it involves a large number of bundles. For CXF-DOSGi having an additional > single-bundle distro helped people getting started quickly, many people move > to the multi-bundle distro later because of its obvious benefits. > > If nobody sees the need for this I'd be happy to keep going without it. It > was just a thought and as I said, an additional distro not replacing the > current assembly... > > Cheers, > > David > > 2009/10/21 Jeremias Maerki <[email protected]> > >> I agree with Filippo. Aggregated bundles kind of defeat the purpose of >> OSGi IMO and causes code duplication at runtime, making memory >> consumption higher than necessary. >> >> On 21.10.2009 12:53:14 Filippo Diotalevi wrote: >> > On Wed, Oct 21, 2009 at 11:29 AM, <[email protected]> wrote: >> > > Hi all, >> > > >> > > [ 0] [Active ] [ ] [ 0] System Bundle (2.0.0) >> > > [ 1] [Active ] [Created ] [ 30] Apache Felix Karaf :: >> Single >> > > Bundle Distro >> > > >> > > If anyone needs to replace or use any of the embedded bundle >> separately, >> > > they can always go back to the current Karaf distro. >> > > >> > > Thoughts anyone? I'd be willing to help out creating this... >> > >> > Honestly, I wouldn't use such a distribution. >> > I need to know which bundles are installed in the container, also >> > considering that there are some bundles that provide significant >> > services (blueprint and fileinstall, to mention the first two), and >> > not only bundles providing APIs. >> > >> > As an alternative solution, I'd enhance the feature paradigm, creating >> > a command to list only the features installed. >> > Something like: >> > >> > features:list --> shows only the features installed, f.i. >> > [ 0] [Active ] [ ] [ 0] System Bundle (2.0.0) >> > [ 1] [Active ] [Created ] [ 30] Apache Felix Karaf :: Basic >> Feature >> > >> > and >> > features:available --> shows all the available features (what is >> > displayed now by features:list) >> > >> > In any case, I would preserve a fine grained bundle list to allow the >> > user to understand what's installed. >> > >> > >> > -- >> > Filippo Diotalevi >> > >> >> >> >> Jeremias Maerki >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
