You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-dev@jackrabbit.apache.org by "Alex Parvulescu (JIRA)" <ji...@apache.org> on 2012/07/31 10:50:34 UTC

[jira] [Resolved] (OAK-211) CompositeEditor should keep the base node state stable

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

Alex Parvulescu resolved OAK-211.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 0.4

integration tests pass, fixed with revision 1367465.

                
> CompositeEditor should keep the base node state stable
> ------------------------------------------------------
>
>                 Key: OAK-211
>                 URL: https://issues.apache.org/jira/browse/OAK-211
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>            Reporter: Alex Parvulescu
>             Fix For: 0.4
>
>
> I noticed that because the base state (the "before" one) changes from one CommitEditor to the next, some editors can miss changes.
> For example I have a composite that contains a validating editor and a lucene editor. because the base state reference changes, the lucene editor assumes that there were no changes.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira