jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tobias Bocanegra" <tobias.bocane...@day.com>
Subject Re: Incremental node type update?!?
Date Tue, 08 Jul 2008 19:30:35 GMT
On 7/8/08, Alexander Klimetschek <aklimets@day.com> wrote:
> Hi Nick,
>
>  if you want a flexible data structure, go with nt:unstructured. Only
>  use node types and mixins for things you know that are fixed and for
>  which you want to search for easily ( //element(*, my:nodetype) ). In
>  this case you have to re-create content and re-register node types
>  from scratch. But a good JCR application creates its initial node
>  types and content model upon first startup with an empty repository
>  anyway. For reset, you can simply delete the workspace folder (if it
>  contains the persistence manager data such as derby files) except for
>  the workspace.xml, and it will get recreated on the next startup of
>  Jackrabbit.
>
>  On Tue, Jul 8, 2008 at 4:33 PM, Nick Stuart <nstuart@speranzasystems.com> wrote:
>  > Is there a way to update node types without have to delete your entire
>  > repository and start over? I dont see a lot of methods on the
>  > NodeTypeManager to allow for really any kind of operation besides
>  > registering types.
>  >
>  > This can't really be an unforseen problem as I imagine data structures are
>  > going to change everywhere, so I think I must be missing something. If I try
>  > to register node types that already exist I of course get an error say its
>  > already there.

if the nodetype change is compatible with the existing one, i.e.
adding a new property or childnode definition, relaxing a constraint,
etc, the node type can be reregistered.

regards, toby

Mime
View raw message