ace-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carsten Ziegeler <>
Subject Re: Using the Sling OSGi Installer?
Date Thu, 24 Nov 2011 10:11:15 GMT
Hi Bram,

no it doesn't support that ootb - actually I saw your bug and that
reminded me of proposing the Sling Installer here (I wanted to do this
for a long time)....

Implementing such an handler for the Sling installer should be easy,
though it requires to implement two service interfaces: the first one
detects the artifact type, the second one does the actual action. We
split this up to be able to add special handling of a certain artifact
type without requiring to reimplement the detection logic.


2011/11/24 Bram de Kruijff <>:
> Hi Carsten,
>> I'm wondering what the general opinion about using the Sling OSGi
>> installer in ACE is?
> does it support metatype (out of the box)? If so, I'll have a look at
> it for amdatu as well :) We just created an artifacthandler for
> fileinstall and submitted it to felix, but no sure if it will make it
> there.. (
> grz
> Bram
> On Thu, Nov 24, 2011 at 8:54 AM, Carsten Ziegeler <> wrote:
>> Hi,
>> 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
>> etc.
>> Just a rough description :)
>> So, in general, WDYT?
>> Regards
>> Carsten
>> --
>> Carsten Ziegeler

Carsten Ziegeler

View raw message