On Fri, Feb 19, 2010 at 10:58 AM, Felix Meschberger <[email protected]> wrote: > ...Maybe this is an option in the form of: launchpad unpacks its resources > in the file system already -- and instead of implementing our own bundle > installation/configuration we just configure a "private FileInstall > instance" to watch over this territory... > > Thus dynamic update is then possible by dropping files there (in > addition to using JCR Install)... > > But this might require some more work to be applied to File Install to > support our SNAPSHOT bundle update and start level support .. (or we > adapt to similar support of File Install, provided it exists already)...
Note that jcrinstall is split in two bundles: jcrinstall watches the repository, and osgi.installer implements the OSGi-related stuff. All the hard stuff is in osgi.installer, jcrinstall just takes care of listening to repository changes and converting repository nodes to InstallableResources for the OsgiInstaller service. Creating a simple folder watcher that talks to the OsgiInstaller service [1] would allow us to reuse the existing osgi.installer semantics (SNAPSHOT handling, config pid encoding etc). Medium-term, merging Felix's FileInstall and our jcrinstall/osgi.installer combo might make sense, of course. -Bertrand [1] http://svn.apache.org/repos/asf/sling/trunk/installer/osgi/installer/src/main/java/org/apache/sling/osgi/installer/OsgiInstaller.java
