[ https://issues.apache.org/jira/browse/JCR-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732987#action_12732987
]
Alfie Kirkpatrick commented on JCR-322:
---------------------------------------
I hacked the Jackrabbit code to always allow node type modifications, regardless of the changes.
This had the effect that after introducing a new required property or child node, existing
nodes could be loaded but couldn't be saved without fixing the problem. This had the desired
effect for me -- leave the application to deal with any migration that needs to be done when
introducing changes. There is a problem restoring versioned nodes since there is an implicit
session save in the restore operation, and therefore no opportunity to fix up a restored node
to make it valid. Perhaps restore could be a two stage process, restore into the session and
then save.
> Support node type modification and removal
> ------------------------------------------
>
> Key: JCR-322
> URL: https://issues.apache.org/jira/browse/JCR-322
> Project: Jackrabbit Content Repository
> Issue Type: New Feature
> Components: nodetype
> Affects Versions: 0.9, 1.0
> Reporter: Jukka Zitting
> Attachments: nodetyperegistry.patch, OKMSystemSession.java
>
>
> There is currently no way to modify or remove registered node types. The existing reregister
and unregister methods in NodeTypeRegistry throw "not yet implemented" exceptions for anything
else than trivial node type changes.
> JSR 283 is working on an node type management API that we should ultimately implement.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.