Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: oak-dev@jackrabbit.apache.org
Received-SPF: pass (nike.apache.org: domain of jukka.zitting@gmail.com
 designates 74.125.82.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4FA7F558.7080004@gmx.de>
References: <4FA7F558.7080004@gmx.de>
From: Jukka Zitting <jukka.zitting@gmail.com>
Date: Mon, 7 May 2012 18:28:04 +0200
Message-ID: 
 <CAOFYJNaqrB6PJkF9pNjVEXmDydAMha-mFczru0x_=DBV99yUzw@mail.gmail.com>
Subject: Re: delegates vs NodeTypeManager
To: oak-dev@jackrabbit.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Hi,

On Mon, May 7, 2012 at 6:16 PM, Julian Reschke <julian.reschke@gmx.de> wrote:
> Would it make sense to split this into a JCR NodetypeManager and
> a Delegate (and do the same for NodeType & frieds)?

Yes, I think we should do that.

However, I'd rather not build information about the
/jcr:system/jcr:nodeTypes tree (or whichever location we use for
storing types) into oak-jcr. Instead that code should IMO be located
in an extra plugin that provides both the NodeTypeManager
functionality to oak-jcr and the required commit validation
functionality to oak-core.

It's pretty rudimentary still, but I've started drafting
o.a.j.oak.plugins as a location for such plugin components. Ultimately
I think those may become their own Maven components, but for now it's
easiest to keep them under .plugins in oak-core.

BR,

Jukka Zitting