[SLING-6159] Implementation should not rely on sling:VanityPath mixin

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Resource Resolver 1.5.0
• Component/s: ResourceResolver
• Assignee: Carsten Ziegeler
• Reporter: Carsten Ziegeler
• Created: 15/Oct/16 14:24
• Updated: 01/Feb/22 16:05
• Resolved: 15/Oct/16 16:05

Description

The handling of vanity paths is since a long time a little bit broken:
on startup a query is done using the mixin sling:VanityPath, from that point on observation is used but only checking the existence of the respective properties, but not the mixin. So it will find/use the props even if the mixin is not set. Then you restart, and these things are gone as the query does not find them.
We should not rely on the mixin at all - we simply use the properties. We do the same for other things like the resource type as well, there is a mixin defined but we don't check it. And mixins are a JCR only concept anyway

Issue Links

• relates to: SLING-11110 ResourceResolver - remove inaccurate mention of sling:VanityPath mixin