On Fri, Jan 29, 2010 at 17:26, Davide Maestroni <[email protected]> wrote: > I wonder if there exists a built-in mechanism to safely updating the nodes > when their type is being changed. What I have in mind is a sort of converter > to register when the type modifications are committed, so to handle the > cases where a node would be no more consistent with its own type. > Can you suggest a way to achieve what I have just describe?
If a node type referenced by a node is no longer available (because it was unregistered, eg. for upgrading the node type), it should fall back to "nt:unstructured". If the definitions no longer match, you might get constraint exceptions upon the next modification of that node (if that modification doesn't "fix" it, eg. by mixins etc.). In general, the best solution to cope with evolving node types is to always use nt:unstructured as base type for your custom node types (or place the residual definitions yourself). And refrain from mandatory properties and child nodes as much as possible. Then you are not forced to update your node types. Regards, Alex -- Alexander Klimetschek [email protected]
