Hi, On Mon, Jul 28, 2008 at 7:33 PM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote: > ...There is already an OSGi specification - the deployment admin specification > - which allows you to package a set of bundles together with configuration. > Without going into details, I think it already covers most of your stuff > ootb....
I had a look and I don't think the deployment admin is what I'm looking for. My goal is to be able to install a bundle by copying the bundle jar file into the JCR repository, in specific locations, along with text files for the configurations. The deployment admin spec, IIUC, is about packaging a bundle and supporting resources (configs, images, etc.) in a jar file, that's not what I'm after. What I'm doing is very similar to jcrinstall (and I'm stealing lots of code from there), the main difference being that my jcrbundles service looks for bundles and configs in all folders named "bundles" under /libs and /apps, so as to keep the application-level bundles close to the scripts that use them. I'm also being more conservative than jcrinstall in the use of JCR observation to detect changes, trying to make the service more robust when it comes to synchronising the OSGi bundles/configs state with what's in the repository after a system restart (including deletion of the sling workdir) for example. For now I'll continue working on my SLING-587 prototype, let people know when it is ready to be tested, and we can then see how much we like (or hate ;-) it. -Bertrand
