[ https://issues.apache.org/jira/browse/JCR-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13815968#comment-13815968
]
Unico Hommes commented on JCR-3690:
-----------------------------------
Patch committed to trunk in revision 1539638, to 2.6 branch in revision 1539639.
> Allow Node Type Registry subclasses to check for conflicting content
> --------------------------------------------------------------------
>
> Key: JCR-3690
> URL: https://issues.apache.org/jira/browse/JCR-3690
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core
> Reporter: Frank van Lankvelt
> Fix For: 2.6.5, 2.7.3
>
> Attachments: JCR-3690.patch
>
>
> The NodeTypeRegistry now throws an exception when a node type is reregistered with non-trivial
changes. There is some commented-out code indicating what should happen in that case, i.e.
check whether conflicting content exists, but that is (obviously) not executed.
> The proposal is to delegate checking whether the diff can be applied to the checkForConflictingContent
method, so that it can determine what to do. Subclasses can then be enriched with namespace-dependent
logic, which may not necessarily involve the full check that is required in principle.
--
This message was sent by Atlassian JIRA
(v6.1#6144)