Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: oak-dev@jackrabbit.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAOFYJNa0J24qzeWhD32sA6oi=d6nPEC4Xj9rzdBYx=J7fAvtnA@mail.gmail.com>
References: 
 <CAB+dfi=Jc1iKgke1b1A2ASpHnkEbqQX67fcsODV53T0arU_fqw@mail.gmail.com>
	<CAOFYJNYfGEWBTvvOm2bTqVd3vsAVoqkBV2ugggXVrtOUMUamQg@mail.gmail.com>
	<CAB+dfikHKM5GoaUd2CSeFhVkf6JX49skLAuA=msmeg8QjRkhhQ@mail.gmail.com>
	<CAOFYJNavY4YUVeB2pJjqpFY3X-UsU0T9Ht=fyjrckS5xV00QOw@mail.gmail.com>
	<CAB+dfi=mkBWk2C678spsA4f340mQRWm2guQe1oYts5B4wf63kg@mail.gmail.com>
	<CAOFYJNbqBFf5ZbjrK_g6+ySTacyBdsiAqgoCYTCmzaDR45C15A@mail.gmail.com>
	<CAB+dfi=iTNG76Y_sFqyfASJk1+=Q1sfvByD1ABh1CO_1YqwXJg@mail.gmail.com>
	<CAOFYJNYOdjB4LuVm2-OD1ufBJqhnEhZg0wM-ccLDHT95-3VcsQ@mail.gmail.com>
	<CAB+dfinqVsQR4y6xTpNRL4u5AJv-PPS--TsXeMBijM5aRKte2A@mail.gmail.com>
	<CAOFYJNa0J24qzeWhD32sA6oi=d6nPEC4Xj9rzdBYx=J7fAvtnA@mail.gmail.com>
Date: Mon, 10 Feb 2014 17:35:18 -0800
Message-ID: 
 <CAB+dfi=Yp+EfgpjmyEJks5b-fFNUErWqBzW3Uc+KUUKE0_70ag@mail.gmail.com>
Subject: Re: Make "Whiteboard" accessible through ContentRepository
From: Tobias Bocanegra <tripod@apache.org>
To: "oak-dev@jackrabbit.apache.org" <oak-dev@jackrabbit.apache.org>
Content-Type: text/plain; charset=UTF-8

Hi,

On Mon, Feb 10, 2014 at 2:55 PM, Jukka Zitting <jukka.zitting@gmail.com> wrote:
> On Mon, Feb 10, 2014 at 5:49 PM, Tobias Bocanegra <tripod@apache.org> wrote:
>> On Mon, Feb 10, 2014 at 1:30 PM, Jukka Zitting <jukka.zitting@gmail.com> wrote:
>>> On Mon, Feb 10, 2014 at 2:50 PM, Tobias Bocanegra <tripod@apache.org> wrote:
>>>> in case of the LoginModules, that's not possible.
>>>
>>> But accessing the whiteboard is? I don't see what's special about the
>>> whiteboard, it's just a service dependency like any other.
>>
>> No, it's a piece of infrastructure, and part of the Oak SPI. I think
>> that components should be able to rely on a system wide Whiteboard if
>> they want.
>> Also, the LoginModules are not 'services' in that sense. they get
>> instantiated by JAAS and can only communicate via Callbacks with the
>> login context.
>
> The thing I don't understand here is why you'd be able to access the
> Whiteboard instance, but not some other service. If it's "not
> possible" to access a reference to a normal service, how would it be
> possible to access a reference to the Whiteboard?

Aha! Because I make the Whiteboard available through the
SecurityProvider.getConfiguration(Whiteboard.class) as a workaround -
but I don't like this. I'd rather offer it via a Callback.

Regards, Toby