jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Updated] (OAK-156) Observation events need Session.refresh
Date Fri, 13 Jul 2012 21:24:33 GMT

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

Michael Dürig updated OAK-156:

    Attachment: OAK-156.patch

This patch implements another solution to solve this: wrapping session calls into a SessionOperation
which provides the necessary context for calling refresh when necessary. This is basically
the same solution we also have in Jackrabbit 2 for handling read/write concurrency. So it
might also come in handy for other problems further down the line.

The patch is very raw and needs further cleaning up. However it demonstrates the idea for
further discussion. 
> Observation events need Session.refresh
> ---------------------------------------
>                 Key: OAK-156
>                 URL: https://issues.apache.org/jira/browse/OAK-156
>             Project: Jackrabbit Oak
>          Issue Type: Sub-task
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>             Fix For: 0.4
>         Attachments: OAK-156.patch
> The observation design from OAK-144 does not deliver events from revisions which are
ahead of the revision on which the current session is based. A call to session.refresh or
session.save will cause such events to be dispatched. 

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


View raw message