[
https://issues.apache.org/jira/browse/SLING-10706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-10706:
------------------------------------
Description:
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.
was:
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.
> 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)
