You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by ChadDavis <ch...@gmail.com> on 2010/01/24 01:14:32 UTC
custom node types
This topic has been discussed at length on this list. But I found one
point unclear.
Someone has pointed out that the "custom_nodetypes.xml" file, which is
created when you programmatically register new node types, can be
copied into another repository. That repository will then pickup
those new node types.
So . . . . why do I need to write any code? Couldn't I just write the
custom_nodetypes.xml file and place it in my repo home, restart and
have the new node types without writing any code?
Re: custom node types
Posted by Alexander Klimetschek <ak...@day.com>.
On Sun, Jan 24, 2010 at 01:14, ChadDavis <ch...@gmail.com> wrote:
> This topic has been discussed at length on this list. But I found one
> point unclear.
>
> Someone has pointed out that the "custom_nodetypes.xml" file, which is
> created when you programmatically register new node types, can be
> copied into another repository. That repository will then pickup
> those new node types.
>
> So . . . . why do I need to write any code? Couldn't I just write the
> custom_nodetypes.xml file and place it in my repo home, restart and
> have the new node types without writing any code?
Because copying it only makes sense if you copy/clone/start a new
repository from scratch. If there are ongoing node type changes via
the JCR / Jackrabbit API, custom_nodetypes.xml will be modified. Also
there is no guarantee that Jackrabbit keeps this node type storing
schema, however registering node types via the JCR API is
standardized.
Regards,
Alex
--
Alexander Klimetschek
alexander.klimetschek@day.com