[
https://issues.apache.org/jira/browse/SLING-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13188006#comment-13188006
]
Felix Meschberger commented on SLING-2371:
------------------------------------------
These are two different issues:
(1) is the original report is the event not properly handled by the Resource
Resolver Mapper
(2) is the Servlet Resolver throwing an NPE upon handling the event (probably
the event is missing some information after some reorg)
I am working on the first under SLING-2321, so I am tempted to resolve this as
a duplicate of that.
> Resource mappings not updated after removing node with vanity path
> ------------------------------------------------------------------
>
> Key: SLING-2371
> URL: https://issues.apache.org/jira/browse/SLING-2371
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Affects Versions: JCR Resource 2.0.10
> Environment: org.apache.sling.jcr.resource-2.0.11-R1205772.jar
> Reporter: Tobias Bocanegra
>
> Steps to reproduce:
> 1. create a node /content/foo with:
> jcr:mixinTypes Name[] sling:VanityPath
> sling:redirect Boolean true
> sling:redirectStatus Long 302
> sling:vanityOrder Long 100
> sling:vanityPath String[] /test
> --> mapping correctly added: ^[^/]+/[^/]+/test(\..*) /content/foo$1
> 2. delete node /content/foo -> mapping not removed
> Restarting the JCR Resource Resolver fixes the problem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
