Carsten Ziegeler resolved SLING-6148.
    Resolution: Fixed

The code of MapEntries seemed to be highly optimized for the way changes used 
to be reported through the Oak observer - now as we switched back to a JCR 
Listener, the changes are reported differently (still correct), but this broke 
the MapEntries.
While working on this, I noticed that there is some room for improvement and 
obviously also test coverage. Created SLING-6153 for this

> MapEntries get CHANGED event right after DELETE
> -----------------------------------------------
>                 Key: SLING-6148
>                 URL: https://issues.apache.org/jira/browse/SLING-6148
>             Project: Sling
>          Issue Type: Bug
>          Components: ResourceResolver
>            Reporter: Bertrand Delacretaz
>            Assignee: Carsten Ziegeler
>            Priority: Critical
>             Fix For: JCR Resource 2.8.2, Resource Resolver 1.5.0
> Investigating SLING-6147 I see this in the logs when deleting a /content node:
> {code}
> 13.10.2016 16:20:23.895 *DEBUG* [oak-executor-17] 
> org.apache.sling.resourceresolver.impl.mapping.MapEntries onChange, 
> type=REMOVED, path=/content
> 13.10.2016 16:20:23.895 *DEBUG* [oak-executor-17] 
> org.apache.sling.resourceresolver.impl.mapping.MapEntries onChange, 
> type=CHANGED, path=/content
> 13.10.2016 16:20:23.895 *DEBUG* [oak-executor-17] 
> org.apache.sling.resourceresolver.impl.mapping.MapEntries doAddVanity getting 
> /content
> {code}
> And MapEntries.isValidVanityPath() then fails as it's getting a null resource.
> [~cziegeler] I suppose this is related to recent listener mechanism changes? 
> Getting a CHANGED event after the DELETE doesn't seem correct.

This message was sent by Atlassian JIRA

Reply via email to