[equinox-dev] [prov] Fw: JcrInstall

[Jeff McAffer <Jeff_McAffer@xxxxxxxxxx>]

I noticed this in the Felix mailing
list.  Our DirectoryWatcher has similar functionality (we too started
with Peter's FileInstaller).  The interesting part of this message
is the JCR stuff.  I believe it is JSR 170 and specs some standards
around repositories.  Might be interesting to look at for ideas in
the p2 context.

Jeff

----- Forwarded by Jeff
McAffer/Ottawa/IBM on 12/20/2007 10:01 PM -----

Felix Meschberger <fmeschbe@xxxxxxxxx>

12/20/2007 03:18 AM

Please respond to
dev@xxxxxxxxxxxxxxxx

To	Felix Dev <dev@xxxxxxxxxxxxxxxx>
cc
Subject	JcrInstall

Hi all,

Inspired by Peter Kriens' FileInstall [1] tool, I created JcrInstall
[2]. This tool works almost exactly as the original FileInstall with the
following differences:

   (1) It operates on a JCR repository [3, 4]
   (2) It uses JCR Observation instead of polling
   (3) It just has a single instance, ergo a single location only

Other than that if works the same:

   * Storing JAR files installes contained bundles
   * Updating JAR files updates the bundles
   * Removing JAR files unsinstalls bundles
   * Storing or updated configuration files (extension is ".cfg")
     creates or updates ConfigurationAdmin configuration
   * Removed configuration files deletes configuration

The full path of JAR files with a prefix of "jcrinstall:" is
used as the
Bundle location. The name (without the path and the .cfg extension) of
configuration files is used to designate the configuration PID. The name
is turned into factory and configuration PID in the same way as for
FileInstall.

A discussion on the Sling developers list [5] showed, that it would make
sense to have this in the Felix project because it could benefit the
OSGi community at large and not just the Sling people.

WDYT ?

Regards
Felix

[1] http://www.aqute.biz/Code/FileInstall
[2]
http://svn.apache.org/repos/asf/incubator/sling/whiteboard/jcrinstall
[3] http://www.jcp.org/en/jsr/detail?id=170
[4] http://jackrabbit.apache.org
[5]
http://www.mail-archive.com/sling-dev@xxxxxxxxxxxxxxxxxxxx/msg01141.html