[jira] Commented: (JCR-1401) Removing-nodes with unexpected nodetype

["Tobias Bocanegra (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JCR-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619511#action_12619511 ] 

Tobias Bocanegra commented on JCR-1401:
---------------------------------------

would it help, if we move the 'replace-the-contentnode-if-wrong-nodetype' logic from the default handler to the XML handler?
in this case, if no XML handler is involved, this would work as before the changes in JCR-973 and an existing content node would not be altered. if the xml handler detects a incompatible node type it would then replace the content node.

> Removing-nodes with unexpected nodetype
> ---------------------------------------
>
>                 Key: JCR-1401
>                 URL: https://issues.apache.org/jira/browse/JCR-1401
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: jackrabbit-jcr-server
>    Affects Versions: 1.4
>            Reporter: Claus Köll
>            Assignee: Tobias Bocanegra
>
> 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 ;-)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.