Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: oak-dev@jackrabbit.apache.org
Received-SPF: unknown (athena.apache.org: error in processing during lookup of
 fmeschbe@adobe.com)
From: Felix Meschberger <fmeschbe@adobe.com>
To: "oak-dev@jackrabbit.apache.org" <oak-dev@jackrabbit.apache.org>
Subject: Re: Make "Whiteboard" accessible through ContentRepository
Thread-Topic: Make "Whiteboard" accessible through ContentRepository
Thread-Index: AQHPJKGg7j3iezxhR0uLEInrs4QTu5qrev8AgAA7J4CAAOykgIABdpSA
Date: Mon, 10 Feb 2014 07:25:48 +0000
Message-ID: <0F640856-7B0A-4881-8335-8E7119AEA37D@adobe.com>
References: 
 <CAB+dfi=Jc1iKgke1b1A2ASpHnkEbqQX67fcsODV53T0arU_fqw@mail.gmail.com>
 <CAOFYJNYfGEWBTvvOm2bTqVd3vsAVoqkBV2ugggXVrtOUMUamQg@mail.gmail.com>
 <CAB+dfikHKM5GoaUd2CSeFhVkf6JX49skLAuA=msmeg8QjRkhhQ@mail.gmail.com>
 <CALMD+rjOoUPDfmT5JF42hgoa29SLUWKY2FMg_2Gusf6aVcyY9w@mail.gmail.com>
In-Reply-To: 
 <CALMD+rjOoUPDfmT5JF42hgoa29SLUWKY2FMg_2Gusf6aVcyY9w@mail.gmail.com>
Accept-Language: de-CH, en-US
Content-Language: en-US
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <B0A16AEA527F594B95B391454616A06D@namprd02.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi

This thread indeed raises the question, why Oak has to come up with somethi=
ng (the Whiteboard) that is almost but not quite like OSGi instead of going=
 all the way through ?

As a stop-gap measure, instead of going full-OSGi you could also just lever=
age the feature, that you really need: The service registry and base on som=
ething like Karl Pauls' =B5Services [2] and PojoSR [3]

Interestingly, when I started with what became Apache Sling I worked on a t=
hing called the "Extension Frameworkg for JCR Repositories" [1] until it tu=
rned out that it basically would be reinventing OSGi =85 and so Sling becam=
e an OSGi application.

Regards
Felix

[1] http://svn.apache.org/repos/asf/jackrabbit/sandbox/inactive/extension-f=
ramework/
[2] http://www.pro-vision.de/content/medialib/pro-vision/production/adaptto=
/2013/adaptto2013-osgi--services-karl-pauls-pdf/_jcr_content/renditions/ren=
dition.download_attachment.file/adaptto2013-osgi--services-karl-pauls.pdf
[3] http://code.google.com/p/pojosr/

Am 09.02.2014 um 10:05 schrieb Davide Giannella <giannella.davide@gmail.com=
>:

> On Sat, Feb 8, 2014 at 6:58 PM, Tobias Bocanegra <tripod@apache.org> wrot=
e:
>> ...
>> ps: I still think we should turn the problem around, and make
>> everything OSGi services and start a small OSGi container for the
>> runtime :-)
>=20
> I was thinking the same tonight. I was going to ask why (any
> historical decisions) Oak in the oak-run doesn't use a simple
> bundled-up OSGi container and runs the related jar, that are already
> OSGi bundles, in it.
>=20
> It would make for example a lot easier to inject a CommitHook like a
> custom index. So far the only way to achieve so is to recompile the
> oak-run adding .with(new MyIndexProvider()) while I'd rather add a
> Service implementation the OSGi whiteboard.
>=20
> D.