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/08/09 16:16:49 UTC
[jira] [Resolved] (OAK-628) Observer not called after Root.commit
[ https://issues.apache.org/jira/browse/OAK-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Dürig resolved OAK-628.
-------------------------------
Resolution: Won't Fix
Fix Version/s: 0.9
Assignee: Michael Dürig
Resolving as won't fix as this is now obsolete with the new observation implementation we have
> Observer not called after Root.commit
> -------------------------------------
>
> Key: OAK-628
> URL: https://issues.apache.org/jira/browse/OAK-628
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core
> Reporter: Michael Dürig
> Assignee: Michael Dürig
> Priority: Minor
> Fix For: 0.9
>
>
> 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