[
https://issues.apache.org/jira/browse/SLING-10706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17397977#comment-17397977
]
Konrad Windszus commented on SLING-10706:
-----------------------------------------
bq. nested identical selectors are not correctly generating a capability
I created SLING-10726 to track that.
Regarding
bq. 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)
There is definitely something fishy going on, but I do not really understand
which capabilities are mandatory in that case. [~radu] Can you create an issue
stating the problem and the expected capabilities for a script like
{{apps/foo/bar/selector1/selector1.html}}? I am not sure which resource types
need to be registered....
> 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)
