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/18 11:55:00 UTC
[jira] [Resolved] (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 resolved SLING-8182.
------------------------------------
Resolution: Fixed
Merged with https://github.com/apache/sling-site/commit/7d1a872f69e66adf7e74b2720f624670a604653c.
> 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
> Assignee: Konrad Windszus
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> 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)