You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Michael Dürig (JIRA)" <ji...@apache.org> on 2013/11/27 09:29:35 UTC
[jira] [Resolved] (OAK-781) Clarify / fix effects of MISSING_NODE
as base state of NodeBuilder
[ https://issues.apache.org/jira/browse/OAK-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Dürig resolved OAK-781.
-------------------------------
Resolution: Fixed
Assignee: Michael Dürig
Fixed by now. Let's follow up with specific issues as necessary.
> 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
> Assignee: Michael Dürig
> Fix For: 0.14
>
> Attachments: 0001-OAK-781-Clarify-fix-effects-of-MISSING_NODE-as-base-.patch, OAK-781-2.patch, OAK-781.patch, OAK-781_reset.patch, memorynodebuilder-1.png, memorynodebuilder-2.png
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)