Hi,

+1 to using fileinstall

One point: I would extend the "fixed" bundles to be installed by the
commons.log bundle, which brings LogService and Logging APIs. This
should IMHO really be the very first bundle to be installed.

Regards
Felix

On 04.08.2010 15:53, Carsten Ziegeler wrote:
> Hi,
> 
> while trying to implement handling of initial configurations for the
> ConfigAdmin within our launchpad, I noticed that this is more difficult
> than I thought. The final problem is a class loading issue as the
> launchpad does not contain the compendium class (for config admin).
> For the same reason, the current support of deployment packages is
> broken in launchpad.
> 
> While trying to workaround these problems I came back to an idea I had a
> long time ago: instead of doing all these installs (bundle, configs,
> depl. pcks etc.) in our own code, why not use existing stuff?
> The FileInstall bundle from Apache Felix covers most of our use cases -
> there are some minor pieces missing. But we can add the required
> features there and avoid duplicate code by just using File Install.
> 
> Currently the launchpad copies the initial set of bundles to a file
> directory and creates a structure based on the start levels there.
> Bundles are then picked up from there and installed.
> 
> Now, I would like to extend this and just copy all files over, bundles
> will get into the same location, all other files go into a single
> "install" directory.
> The only bundle which we will really install by launchpad is the File
> Install bundle - which will be configured to listen for the directory
> where everything got copied over.
> 
> File Install picks up the bundles with the start levels, the configs and
> whatnot and just installs the stuff for us. As the directory is watched
> by File Install, changes are reflected as well.
> 
> So basically we have the same functionality with less code :)
> 
> I think getting all of this done for Sling 6 is too much. Therefore I
> would like to use File Install for everything else but bundles as a
> start: copying over those files to the install directory and start file
> install configured with that directory.
> 
> Note, that File Install is mainly used to get initial configuration into
> the system - so it's more bootstrapping - for everything else jcr
> install can be used. Or File Install is nice for all those scenarios
> where no repository is used :)
> 
> WDYT?
> 
> Carsten

Reply via email to