On Tuesday 23 September 2014 21:18:14 David Bosschaert wrote: > Hi all, hi David,
> After presenting at Adaptto about OSGi subsystems [1] the idea came > about to maybe add an alternative launchpad distribution that is > basically an OSGi subsystem archive (.esa) file. This would allow you > to deploy Sling into an existing OSGi framework in one shot if that > framework has OSGi subsystem support. > > I tried to create a basic subsystem from the existing launchpad > configuration, but I have to admit that my approach is pretty naive > and was just based on repackaging the existing launchpad. You can see > my attempt here [2] and I am not at all suggesting that we continue > that. It might be better to do something with the esa-maven-plugin [3] > instead. > > The script at [2] does generate an .esa file, but it didn't really > work for me. After copying all the sling.properties to the normal > Felix config.properties everything resolves, but going to > http://localhost:8080 gives me a 403 instead of the default launching > page. > > So I guess my attempt is more or less a failed experiment, but I'm > wondering if other people might have a better idea on how to create a > subsystem archive for Sling? I hope to have some time next week to look into it and the common model Carsten and Bertrand are working on. For Karaf we now have several features and you only need to install what your application needs. Do you plan something similar with subsystems or will there be only one subsystem for Sling? @Carsten, Bertrand: is the common model able to represent such dependencies between subsystems/features? @David: did you make progress with esa-maven-plugin? Regards, O. > Cheers, > > David > > [1] > http://adapt.to/2014/en/schedule/using-osgi-subsystems-with-apache-felix.h > tml [2] > https://github.com/bosschaert/sling/commit/9782d38aa131d84388ff0fdba6e4834 > d83d7db1a [3] http://aries.apache.org/modules/esamavenpluginproject.html
