You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Tobias Bocanegra (JIRA)" <ji...@apache.org> on 2006/05/18 00:26:05 UTC
[jira] Created: (JCR-435) Node.update() does not work correct for
SNS
Node.update() does not work correct for SNS
-------------------------------------------
Key: JCR-435
URL: http://issues.apache.org/jira/browse/JCR-435
Project: Jackrabbit
Type: Bug
Versions: 1.0, 0.9
Reporter: Tobias Bocanegra
when node to be updated contains same-name-sibblings, only the first child is resepcted:
W1:
/a
/b
- p1
/b
W2:
/a
/b
now a W2."/a/b".update() iteratates over the child nodes of "a" and updates "b" twice.
btw: in the case where property p1 is binary, and internally kept in a tmp-file, the tmp-file gets discarded and an exception is thrown when storing the changes. this might explain some issues discribed in JCR-428.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (JCR-435) Node.update() does not work correct for
SNS
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-435?page=all ]
Jukka Zitting updated JCR-435:
------------------------------
Fix Version/s: (was: 1.1)
> Node.update() does not work correct for SNS
> -------------------------------------------
>
> Key: JCR-435
> URL: http://issues.apache.org/jira/browse/JCR-435
> Project: Jackrabbit
> Issue Type: Bug
> Components: core
> Affects Versions: 0.9, 1.0, 1.0.1
> Reporter: Tobias Bocanegra
> Assigned To: Tobias Bocanegra
>
> when node to be updated contains same-name-sibblings, only the first child is resepcted:
> W1:
> /a
> /b
> - p1
> /b
> W2:
> /a
> /b
> now a W2."/a/b".update() iteratates over the child nodes of "a" and updates "b" twice.
> btw: in the case where property p1 is binary, and internally kept in a tmp-file, the tmp-file gets discarded and an exception is thrown when storing the changes. this might explain some issues discribed in JCR-428.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (JCR-435) Node.update() does not work correct for
SNS
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-435?page=all ]
Jukka Zitting updated JCR-435:
------------------------------
Component: core
Fix Version: 1.1
Version: 1.0.1
> Node.update() does not work correct for SNS
> -------------------------------------------
>
> Key: JCR-435
> URL: http://issues.apache.org/jira/browse/JCR-435
> Project: Jackrabbit
> Type: Bug
> Components: core
> Versions: 0.9, 1.0, 1.0.1
> Reporter: Tobias Bocanegra
> Assignee: Tobias Bocanegra
> Fix For: 1.1
>
> when node to be updated contains same-name-sibblings, only the first child is resepcted:
> W1:
> /a
> /b
> - p1
> /b
> W2:
> /a
> /b
> now a W2."/a/b".update() iteratates over the child nodes of "a" and updates "b" twice.
> btw: in the case where property p1 is binary, and internally kept in a tmp-file, the tmp-file gets discarded and an exception is thrown when storing the changes. this might explain some issues discribed in JCR-428.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (JCR-435) Node.update() does not work correct for
SNS
Posted by "Tobias Bocanegra (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-435?page=all ]
Tobias Bocanegra reassigned JCR-435:
------------------------------------
Assign To: Tobias Bocanegra
> Node.update() does not work correct for SNS
> -------------------------------------------
>
> Key: JCR-435
> URL: http://issues.apache.org/jira/browse/JCR-435
> Project: Jackrabbit
> Type: Bug
> Versions: 1.0, 0.9
> Reporter: Tobias Bocanegra
> Assignee: Tobias Bocanegra
>
> when node to be updated contains same-name-sibblings, only the first child is resepcted:
> W1:
> /a
> /b
> - p1
> /b
> W2:
> /a
> /b
> now a W2."/a/b".update() iteratates over the child nodes of "a" and updates "b" twice.
> btw: in the case where property p1 is binary, and internally kept in a tmp-file, the tmp-file gets discarded and an exception is thrown when storing the changes. this might explain some issues discribed in JCR-428.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (JCR-435) Node.update() does not work correct for
SNS
Posted by "Stefan Guggisberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Guggisberg updated JCR-435:
----------------------------------
Component/s: (was: jackrabbit-core)
versioning
> Node.update() does not work correct for SNS
> -------------------------------------------
>
> Key: JCR-435
> URL: https://issues.apache.org/jira/browse/JCR-435
> Project: Jackrabbit
> Issue Type: Bug
> Components: versioning
> Affects Versions: 0.9, 1.0, 1.0.1
> Reporter: Tobias Bocanegra
> Assignee: Tobias Bocanegra
>
> when node to be updated contains same-name-sibblings, only the first child is resepcted:
> W1:
> /a
> /b
> - p1
> /b
> W2:
> /a
> /b
> now a W2."/a/b".update() iteratates over the child nodes of "a" and updates "b" twice.
> btw: in the case where property p1 is binary, and internally kept in a tmp-file, the tmp-file gets discarded and an exception is thrown when storing the changes. this might explain some issues discribed in JCR-428.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.