[jira] [Commented] (SLING-6710) Vanity Path might get removed if a resource is updated
[ https://issues.apache.org/jira/browse/SLING-6710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15940666#comment-15940666 ] Carsten Ziegeler commented on SLING-6710: - Added a test case in rev 1788498 which fails in 1.5.20 but passes with the above applied fix > Vanity Path might get removed if a resource is updated > -- > > Key: SLING-6710 > URL: https://issues.apache.org/jira/browse/SLING-6710 > Project: Sling > Issue Type: Bug > Components: ResourceResolver >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Blocker > Fix For: Resource Resolver 1.5.22 > > > Assume there is a resource at /libs/foo which has a child resource > /libs/foo/jcr:content with a vanity path. If now /libs/foo is updated, the > current implementation first removes the vanity path for /libs/foo (as > defined in the child resource jcr:content) but then fails to re-add it as it > does not take the jcr:content child resource into account. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SLING-6710) Vanity Path might get removed if a resource is updated
[ https://issues.apache.org/jira/browse/SLING-6710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15940615#comment-15940615 ] Carsten Ziegeler commented on SLING-6710: - Updated the implementation in rev 1788490 to check the updated resource and also check for a potential child resource named jcr:content In addition improved the handling of update and discard invalid paths as quickly as possible > Vanity Path might get removed if a resource is updated > -- > > Key: SLING-6710 > URL: https://issues.apache.org/jira/browse/SLING-6710 > Project: Sling > Issue Type: Bug > Components: ResourceResolver >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Blocker > Fix For: Resource Resolver 1.5.22 > > > Assume there is a resource at /libs/foo which has a child resource > /libs/foo/jcr:content with a vanity path. If now /libs/foo is updated, the > current implementation first removes the vanity path for /libs/foo (as > defined in the child resource jcr:content) but then fails to re-add it as it > does not take the jcr:content child resource into account. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
