You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Claus Köll (JIRA)" <ji...@apache.org> on 2008/02/20 14:49:43 UTC
[jira] Created: (JCR-1401) Removing-nodes with unexpected nodetype
Removing-nodes with unexpected nodetype
---------------------------------------
Key: JCR-1401
URL: https://issues.apache.org/jira/browse/JCR-1401
Project: Jackrabbit
Issue Type: Improvement
Components: jackrabbit-webdav
Affects Versions: 1.4
Reporter: Claus Köll
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.
[jira] Resolved: (JCR-1401) Removing-nodes with unexpected nodetype
Posted by "Tobias Bocanegra (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tobias Bocanegra resolved JCR-1401.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.5
1.4.1
fixed in 1.4 branch, rev. 682477.
fixed in trunk, rev. 682481.
> 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: 1.4.1, 1.5
>
>
> 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.
[jira] Assigned: (JCR-1401) Removing-nodes with unexpected nodetype
Posted by "Tobias Bocanegra (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tobias Bocanegra reassigned JCR-1401:
-------------------------------------
Assignee: Tobias Bocanegra
> 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.
[jira] Updated: (JCR-1401) Removing-nodes with unexpected nodetype
Posted by "angela (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (JCR-1401) Removing-nodes with unexpected
nodetype
Posted by "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.
[jira] Updated: (JCR-1401) Removing-nodes with unexpected nodetype
Posted by "angela (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
angela updated JCR-1401:
------------------------
Component/s: (was: jackrabbit-webdav)
jackrabbit-jcr-server
wrong component. should be: jcr-server
> 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
>
> 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.
[jira] Commented: (JCR-1401) Removing-nodes with unexpected
nodetype
Posted by "Claus Köll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619515#action_12619515 ]
Claus Köll commented on JCR-1401:
---------------------------------
that sounds good for me ...
thanks
claus
> 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.