[JCR-1401] Removing-nodes with unexpected nodetype

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.4
• Fix Version/s: jcr-server 1.4.1
• Component/s: jackrabbit-jcr-server
• Assignee: Tobias Bocanegra
• Reporter: Claus Köll
• Created: 20/Feb/08 13:49
• Updated: 29/Sep/08 14:47
• Resolved: 04/Aug/08 19:46

Description

tobias adds a logic with JCR-973 that the DefaultHandler checks the nodetype of the jcr:content node
and if it does not match it will be deleted and created with the new one.
i think its dangerous to automacially change a node type.
if the node was added programatically and then saved through webdav it could happen that the nodetype will be changed
from nt:resource to the nt:unstructured.
if some logic depends on the nodetype the failure search will be hard