[
https://issues.apache.org/jira/browse/SLING-10706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17394855#comment-17394855
]
Konrad Windszus commented on SLING-10706:
-----------------------------------------
According to
https://sling.apache.org/documentation/the-sling-engine/url-to-script-resolution.html#script-naming-conventions
it would be indeed
{code}
/apps/scripts/myscript/sel1/sel1.html
{code}
That should resolve for request to {{/content/my.sel1.sel1.html}} given that
{{/content/my}} has the resource type {{/apps/scripts/myscript}}.
Whether that script additionally resolves for {{/content/mysel1.sel1.html}}
given that {{/content/mysel1}} has the resource type
{{/apps/scripts/myscript/sel1}} does not really matter in this context.
> Order of selectors not kept
> ---------------------------
>
> Key: SLING-10706
> URL: https://issues.apache.org/jira/browse/SLING-10706
> Project: Sling
> Issue Type: Bug
> Components: Maven Plugins and Archetypes
> Affects Versions: Scripting Bundle Maven Plugin 0.3.0
> Reporter: Konrad Windszus
> Priority: Major
> Fix For: Scripting Bundle Maven Plugin 0.4.0
>
>
> The selectors used for registration of script/servlets have an order: Only if
> they appear in the given order the script/servlet matches
> (https://sling.apache.org/documentation/the-sling-engine/servlets.html#servlet-registration).
> The order is potentially lost, though during the generation of the
> capabilities headers as the code is using Sets internally.
> Also it is totally valid to register a script to "myselector.myselector"
> which cannot be expressed with Sets either.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
