Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (nike.apache.org: domain of stefan.guggisberg@gmail.com
 designates 209.85.146.176 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=GUc2gdqtinE/5zGETojMwu2Ds37sURgsHzLg665Fp9ip/gsHUNdx7VTJhOGTvgMskqtap0PO1G3hPZ2IQjDcpgmeLuTgvQX/BWVAx1RuW2X2GRw3b8bo/XaWgSnhuSFrQO8U2KN1Wn75IrsEdtAdT+eDL2+0JoFNgJ6YGuWRzZU=
Message-ID: <90a8d1c00802180539k334809coa290695230cff9aa@mail.gmail.com>
Date: Mon, 18 Feb 2008 14:39:02 +0100
From: "Stefan Guggisberg" <stefan.guggisberg@gmail.com>
To: users@jackrabbit.apache.org
Subject: Re: Deploying custom node types in jackrabbit
In-Reply-To: <82133d700802180426y6dc15c79x9b66eafc289c7a1f@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <82133d700802161410i22fd8598r2b5cf597c02caf77@mail.gmail.com>
	 <90a8d1c00802180207j40d4cb84qa84e9dad8c110bb4@mail.gmail.com>
	 <82133d700802180426y6dc15c79x9b66eafc289c7a1f@mail.gmail.com>

On Feb 18, 2008 1:26 PM, Manolo Gomez Lopez <performante@gmail.com> wrote:
> Hi Stefan
>
> 2008/2/18, Stefan Guggisberg <stefan.guggisberg@gmail.com>:
> >
> >
> >
> > > there was a related feature request:
> > > http://issues.apache.org/jira/browse/JCR-771
> >
> > > cheers
> > > stefan
>
>
>
> I must admit I dind't see that one before asking, sorry.
>
> I agree that maybe using the current internal serialization of custom node
> types (in repository/nodetypes)  is not the best solution for helping in the
> deployment of custom node types (but certain not as hard as modifying an
> Oracle tablespace ;)).
>
> But I also see that forcing an API method invocation as the *only* way of
> registering node types maybe is not the best solution for all deployment
> scenarios.
>
> I am thinking in large deployments of pre-configured jackrabbit registries
> with lots of custom node types..., providing a way to give jackrabbit
> representations of the custom node types in CND format in some way at start
> time (other than via API) will certainly ease the deployment of those
> repositories.
>
> I am sure that already having an independent representation of custom node
> types and namespaces in CND (or its counterpart in XML) are solid
> foundations for the implementation os this feature.
>
> Don't you think this feature is worth a try and will be a good improvement
> for jackrabbit?

while i agree it could be very convenient in certain scenarios i guess
it can cause
a lot of trouble (how do you handle removed types, illegal
definitions, unsupported
changes  etc) if supported in core during bootstrapping. while editing
a text based
definition is certainly trivial, the effects of such changes might be dramatic.

OTOH i think such a feature could be easily implemented as an external
tool/service.
WDYT?

cheers
stefan

>
> Greets,
>