You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2018/12/17 11:30:00 UTC
[jira] [Updated] (SLING-8182) Add documentation about servlet
resolution order
[ https://issues.apache.org/jira/browse/SLING-8182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus updated SLING-8182:
-----------------------------------
Description:
The documentation at https://sling.apache.org/documentation/the-sling-engine/servlets.html#servlet-registration should include a paragraph about the order in which potential matching servlets/scripts are considered.
Aspects to be covered:
* Consideration of property {{service.ranking}}
* Amount of matching selectors and extension
* Location of the matching resource type in the inheritance tree
* OptingServlet vs. regular servlet
was:
The documentation at https://sling.apache.org/documentation/the-sling-engine/servlets.html#servlet-registration should include a paragraph about the order in which potential matching servlets/scripts are found.
Aspects to be covered:
* Consideration of property {{service.ranking}}
* Amount of matching selectors and extension
* Location of the matching resource type in the inheritance tree
> Add documentation about servlet resolution order
> ------------------------------------------------
>
> Key: SLING-8182
> URL: https://issues.apache.org/jira/browse/SLING-8182
> Project: Sling
> Issue Type: Improvement
> Components: Documentation
> Reporter: Konrad Windszus
> Priority: Major
>
> The documentation at https://sling.apache.org/documentation/the-sling-engine/servlets.html#servlet-registration should include a paragraph about the order in which potential matching servlets/scripts are considered.
> Aspects to be covered:
> * Consideration of property {{service.ranking}}
> * Amount of matching selectors and extension
> * Location of the matching resource type in the inheritance tree
> * OptingServlet vs. regular servlet
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)