[
https://issues.apache.org/jira/browse/SLING-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13957551#comment-13957551
]
Michael Dürig commented on SLING-3487:
--------------------------------------
I think in the {{JcrResourceListener}} case the session refresh logic of Oak
should kick in and the explicit refresh should not be necessary. But it will
hopefully not do any harm. In the pure Oak case there is no such auto
refreshing as there the listener is not attached to a session.
> Resource added events missing when using new OakResourceListener
> ----------------------------------------------------------------
>
> Key: SLING-3487
> URL: https://issues.apache.org/jira/browse/SLING-3487
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Affects Versions: JCR Resource 2.3.6
> Reporter: Marc Pfaff
> Assignee: Michael Dürig
> Priority: Critical
> Fix For: JCR Resource 2.3.8
>
> Attachments: SLING-3487.patch
>
>
> The newly introduced OakResourceListener in SLING-3279 seem's to fail
> dispatching all oak observation into resource added events.
> There seem's to be a missing resolver refresh, which prevents
> OakResouceListener to resolve the path's from the observation properly as the
> resources are not found from time to time.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
