[jira] [Resolved] (SLING-3440) Clarify script resolution documentation with regard to selectors

["Konrad Windszus (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konrad Windszus resolved SLING-3440.
------------------------------------
    Resolution: Fixed

> Clarify script resolution documentation with regard to selectors
> ----------------------------------------------------------------
>
>                 Key: SLING-3440
>                 URL: https://issues.apache.org/jira/browse/SLING-3440
>             Project: Sling
>          Issue Type: Improvement
>          Components: Documentation
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>
> The documentation around URL to Script Resolution [1] is very good, except for three points.
> a) The resourceType given in the example is confusing. Rather than sling:sample, please make that sling/sample. Maybe you could add a hint, that if no resourceType is given, the fallback is to use the primary node type.
> b) You should explicitly mention that the order of selectors is relevant.
> c) You should mention that if less selectors are given in the script name than are given in the request, the selectors given in the script name must be the first selectors from the request (to be a potential match). Maybe an example would be good
> i.e. script name is print/a4.esp 
> and the request is
> 1) <some resource>.print.a4.unspecifiedselector.html (matches)
> 2) <some resource>.unspecifiedselector.print.a4.html (does not match)
> [1] - http://sling.apache.org/documentation/the-sling-engine/url-to-script-resolution.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)