jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-1401) Removing-nodes with unexpected nodetype
Date Wed, 24 Sep 2008 13:52:44 GMT

     [ https://issues.apache.org/jira/browse/JCR-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

angela updated JCR-1401:
------------------------

    Fix Version/s:     (was: 1.5)
                       (was: 1.4.1)
                   jcr-server 1.4.1

> 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
>             Fix For: jcr-server 1.4.1
>
>
> 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.


Mime
View raw message