Hi, On Mon, Jan 27, 2014 at 11:48 AM, Michael Dürig <[email protected]> wrote: > Have a look at the EventGenerator constructor before your changes. There you > could pass in a Listener instance which then would receive the respective > call backs. The JcrListner class was just one such Listener implementation, > materialising the call backs to EventImpl instances. The idea was that low > level implementation could use this for their own purposes when a different > materialisation was needed (e.g. including jcr:content).
OK, thanks. It seemed as if this mechanism was no longer used as the EventIterable class overrode key parts of it to postpone traversal of the changed subtrees. How about I restore the mechanism, but in a way that generalizes the nice continuation feature you added for JCR events? BR, Jukka Zitting
