Hi Jim, can you please provide sample code, which shows the behaviour you see? I'm particularly interested in what exactly you mean when you write 'not always up-to-date'.
Regards Marcel On 05/05/15 21:16, "Jim.Tully" <jim.tu...@target.com> wrote: >Hi, > >We are using Oak in one of our applications, and have come up with a >problem that I can¹t seem to find an answer to. > >We have an Event Listener registered to listen for changes to properties >in a node. It is always notified of the events properly. Upon >notification, the listener retrieves the Node from the session, and >performs various actions depending on the properties set on the node. > >However, if the node is versioned, the node that is retrieved from the >JCR is not always up-to-date, even if a new session is used to retrieve >it. I assume that this is because versioning introduces a delay in the >³save². Is there a way to work around this, short of forcing an >arbitrary wait before attempting to retrieve the node? > >Thanks > >Jim
