[
https://issues.apache.org/jira/browse/SLING-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13957533#comment-13957533
]
Carsten Ziegeler commented on SLING-3487:
-----------------------------------------
I made a modification to the patch which refreshes the resolver if the jcr
bridge is used as well. I believe this is required if used within Oak, too
> 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)
