[
https://issues.apache.org/jira/browse/SLING-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15575705#comment-15575705
]
Carsten Ziegeler commented on SLING-3558:
-----------------------------------------
[~asanso] I think the handling of vanity paths is slightly broken in MapEntries.
On initial startup, a query is performed, explicitely searching for resources
with the mixin set and only those are used
During runtime, the mixin is not checked at all anymore - so if a new node with
the correct property - but without the mixin - is added, it gets picked up.
Therefore after removal of the mixin, the vanity path is still used.
I think we should change the implementation to use the vanitypath property on
any resource regardless if the mixin is set, other resource providers don't
have the concept of mixins
> Updating of sling:VanityPath mixins is ignored by sling resource resolution
> ---------------------------------------------------------------------------
>
> Key: SLING-3558
> URL: https://issues.apache.org/jira/browse/SLING-3558
> Project: Sling
> Issue Type: Bug
> Components: ResourceResolver
> Reporter: Antonio Sanso
> Priority: Critical
>
> Updating (adding/removing) of sling:VanityPath mixins is ignored by sling
> resource resolution. The reason behind it is that the event handler in the
> MapEntries doesn't listen for sling:VanityPath (mixin) but only for
> sling:vanityPath (property name).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
