You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Radu Cotescu (Jira)" <ji...@apache.org> on 2021/08/06 16:20:00 UTC

[jira] [Comment Edited] (SLING-10706) Order of selectors not kept

    [ https://issues.apache.org/jira/browse/SLING-10706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17394869#comment-17394869 ] 

Radu Cotescu edited comment on SLING-10706 at 8/6/21, 4:19 PM:
---------------------------------------------------------------

I see your point, but then I think we need to rephrase this issue and state the actual problems:
# nested identical selectors are not correctly generating a capability
# nested resource types should contribute selector scripts to resource types higher in the file hierarchy (I think we're filtering this in the plugin right now)


was (Author: radu.cotescu):
I see your point, but then I think we need to rephrase this issue and state the actual problems:
1. nested identical selectors are not correctly generating a capability
2. nested resource types should contribute selector scripts to resource types higher in the file hierarchy (I think we're filtering this in the plugin right now)

> 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)