[
https://issues.apache.org/jira/browse/JCR-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462464
]
Sandro Boehme commented on JCR-322:
-----------------------------------
People in the mailling list sometimes say that a deep lock is needed
and that this is a big problem in this issue.
I guess it is needed to avoid the new creation of nodes after
the search for nodes with the node type that has to be unregistered.
If that's the case maybe there is a way to avoid the deep lock.
If a user tries to add a node with a node type that is currently
being unregistered a NodeTypeNotFoundException (or similar) could
already be thrown. This way it's possible to search for all nodes with
this type and change the type to nt:base while the amount of nodes
with this type will not change anymore.
To search for nodes by type the following query should work
"//element(*, nt:nodeType)". Of course this needs to be done for
every workspace.
Do you think that could work?
> Support node type modification and removal
> ------------------------------------------
>
> Key: JCR-322
> URL: https://issues.apache.org/jira/browse/JCR-322
> Project: Jackrabbit
> Issue Type: New Feature
> Components: nodetype
> Affects Versions: 0.9, 1.0
> Reporter: Jukka Zitting
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
