Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: oak-dev@jackrabbit.apache.org
Date: Thu, 28 Jun 2012 15:26:42 +0000 (UTC)
From: "Jukka Zitting (JIRA)" <jira@apache.org>
To: oak-dev@jackrabbit.apache.org
Message-ID: <911764841.66973.1340897203847.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <1392993864.66965.1340896964479.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (OAK-156) Observation events need
 Session.refresh
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/OAK-156?page=3Dcom.atlassian.ji=
ra.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1340316=
3#comment-13403163 ]=20

Jukka Zitting commented on OAK-156:
-----------------------------------

I'd solve this by having a timer periodically refresh() a session that has =
registered an observation listener.
               =20
> 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=C3=BCrig
>
> The observation design from OAK-144 does not deliver events from revision=
s 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 dispat=
ched.=20

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