Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: oak-dev@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of ianboston@gmail.com
 designates 209.85.220.175 as permitted sender)
MIME-Version: 1.0
Sender: ianboston@gmail.com
In-Reply-To: 
 <CAOFYJNZGS2JR+xuWxNybXbwVsngjub6ogBaOwCqyrn2rCq7Vog@mail.gmail.com>
References: 
 <CAH=Gj-=szn73BubT6JLFcmLJyXJ8Hfm11974by8NhFFYtQhqew@mail.gmail.com>
	<CAOFYJNZGS2JR+xuWxNybXbwVsngjub6ogBaOwCqyrn2rCq7Vog@mail.gmail.com>
Date: Tue, 2 Apr 2013 23:34:34 +1100
Message-ID: 
 <CAH=Gj-mc78bWr7gRL7ahX7_rLJVamatFzT4PuYBDoS_u2qGy9g@mail.gmail.com>
Subject: Re: NodeStore or MicroKernel.
From: Ian Boston <ieb@tfd.co.uk>
To: "oak-dev@jackrabbit.apache.org" <oak-dev@jackrabbit.apache.org>
Content-Type: multipart/alternative; boundary=14dae9ccd516bed56704d95ff57e

--14dae9ccd516bed56704d95ff57e
Content-Type: text/plain; charset=ISO-8859-1

On Tuesday, April 2, 2013, Jukka Zitting wrote:

> Hi,
>
> On Thu, Mar 28, 2013 at 9:39 AM, Ian Boston <ieb@tfd.co.uk <javascript:;>>
> wrote:
> > Should I depend on a reference of a MicroKernel or a NodeStore when
> > constructing the Oak class (new
> > Oak(?).when(....).createContentRepositroy()) ?
>
> It's better if you use the Oak(NodeStore) signature as that'll work
> also with the SegmentMK backend that implements just the NodeStore
> interface instead of MicroKernel. The Oak(MicroKernel) signature just
> wraps the given MicroKernel instance to a KernelNodeStore.


Good to know, I'll switch to nodestore.


>
> > I see there are a number of providers in the oak-core bundle. Should I
> > use these to build the Oak class or is it Ok to build it from internal
> > instances ?
>
> You mean the OSGi services that oak-core provides?


Yes.


>
> It's still a bit of an open question whether the core repository
> should be wired up entirely through OSGi or have some of the core
> components (security, node type validation, etc.) injected directly
> with Oak.with() as hardcoded parts. The latter approach (coupled with
> hooks to bring in also more dynamic OSGi services) might be better as
> it gives us more control over repository startup.


Ok, I think I am going to go with direct injection, but I suspect it will
be easy to change later if required.

One last question.
Should I expect a a SecurityConfiguration to be present ?

I have loaded the Felix JAAS boot bundle, and configured all the
LoginModules listed in the oak-core bundle ( btw, there is a comma missing
in the pom.xml ) but I still get an error message saying no Security
Configuration is available from JAAS, on login attempts.

Thanks
Ian


>
> BR,
>
> Jukka Zitting
>

--14dae9ccd516bed56704d95ff57e--