ace-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carsten Ziegeler <>
Subject Using the Sling OSGi Installer?
Date Thu, 24 Nov 2011 07:54:58 GMT

I'm wondering what the general opinion about using the Sling OSGi
installer in ACE is?

The installer is not tied to Sling it just happens that we have
developed it as part of the project. It's a general purpose installer
which ootb is able to handle bundles and configurations like
FileInstall. The main difference is that we separated the actual
handling of the artifacts from the providers. So the installer itself
is handling installation, update, and removal of artifacts and there
are different plugins providing those artifacts.
One of these plugins is a file provider (which basically works like
FileInstall), another one (different bundle) reads artifacts from a
JCR repository and so on.

In addition, the installer handles retries, keeps state of what it did
install and detects if a user did some manual changes. For example,
you install bundle A in version 1.0 through the installer, the user
updates this bundle to version 1.1 through the web console. Now you
remove the 1.0 artifact from the directory. In this case, the 1.1
version should still be active and not be uninstalled. And so on.

Oh, and like with FileInstall it's possible to add support for other
artifact types. For example we have support for deployment packages

Just a rough description :)

So, in general, WDYT?

Carsten Ziegeler

View raw message