[
https://issues.apache.org/jira/browse/OAK-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated OAK-781:
------------------------------
Attachment: 0001-OAK-781-Clarify-fix-effects-of-MISSING_NODE-as-base-.patch
The attached patch contains a quick draft of the proposed new methods:
{{exists()}}, {{getChild(String)}} and {{addChild(String)}}. Note that the
{{addChild}} method, as drafted, is actually equivalent to {{setNode(name,
EMPTY_NODE)}}.
The implementation in {{MemoryNodeBuilder}} will probably need some more
thought, and we'd need to update at least {{TreeImpl}} and a few other cases to
use the new methods instead of always calling {{child(String)}}.
> Clarify / fix effects of MISSING_NODE as base state of NodeBuilder
> ------------------------------------------------------------------
>
> Key: OAK-781
> URL: https://issues.apache.org/jira/browse/OAK-781
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
> Reporter: Michael Dürig
> Attachments:
> 0001-OAK-781-Clarify-fix-effects-of-MISSING_NODE-as-base-.patch
>
>
> Having a {{MISSING_NODE}} respectively a node state that returns false for
> its {{exists}} method as a base state of a node builder results in undefined
> behaviour. We need to clarify how to handle such cases for resolving OAK-766.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
