[
https://issues.apache.org/jira/browse/OAK-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579056#comment-13579056
]
Jukka Zitting commented on OAK-628:
-----------------------------------
OK as long as we avoid the possibility of an observer reporting some changes
before they become visible through {{NodeStore.getRoot}}. We also need to make
sure that consecutive calls to the same observer receive a continuous sequence
of root states, i.e. the {{after}} state of one call always becomes the
{{before}} state of the next one.
> Observer not called after Root.commit
> -------------------------------------
>
> Key: OAK-628
> URL: https://issues.apache.org/jira/browse/OAK-628
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
> Reporter: Michael Dürig
>
> Currently {{Observer.contentChanged}} is not called after a successful
> {{Root.commit}} but rather on the next call to {{NodeStore.getRoot}}. In
> order to move it closer to when the actual changes took place I think we
> should call {{Observer.contentChanged}} right after a successful commit.
--
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
