[
https://issues.apache.org/jira/browse/SLING-9965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-9965:
-----------------------------------
Description:
With the addition of SLING-9406 one can register scripts not only via the
ResourceResolver but also via OSGi bundles. Unfortunately the configuration
property {{servletresolver.paths}} for PID
{{org.apache.sling.servlets.resolver.SlingServletResolver}} has not been
extended, that means if the same script is registered both via Resource
Resolver and Bundle it seems that always the bundled one takes precedence.
The default resolution order should be clarified in
https://sling.apache.org/documentation/the-sling-engine/servlets.html#servlet-resolution-order.
Also it should be possible to influence the order of precedence via OSGi
configuration.
In addition it should be clarified if embedded or precompiled scripts take
preference
(https://github.com/apache/sling-org-apache-sling-servlets-resolver#so-how-do-i-deploy-my-scripts).
IMHO the resolution order is as follows
1. precompiled scripts
2. embedded scripts
3. resource resolver scripts
was:
With the addition of SLING-9406 one can register scripts not only via the
ResourceResolver but also via OSGi bundles. Unfortunately the configuration
property {{servletresolver.paths}} for PID
{{org.apache.sling.servlets.resolver.SlingServletResolver}} has not been
extended, that means if the same script is registered both via Resource
Resolver and Bundle it seems that always the bundled one takes precedence.
The default resolution order should be clarified in
https://sling.apache.org/documentation/the-sling-engine/servlets.html#servlet-resolution-order.
Also it should be possible to influence the order of precedence via OSGi
configuration.
> Clarify resolution order of bundled scripts vs resource resolver scripts
> ------------------------------------------------------------------------
>
> Key: SLING-9965
> URL: https://issues.apache.org/jira/browse/SLING-9965
> Project: Sling
> Issue Type: Improvement
> Components: Servlets
> Affects Versions: Servlets Resolver 2.7.10
> Reporter: Konrad Windszus
> Priority: Major
>
> With the addition of SLING-9406 one can register scripts not only via the
> ResourceResolver but also via OSGi bundles. Unfortunately the configuration
> property {{servletresolver.paths}} for PID
> {{org.apache.sling.servlets.resolver.SlingServletResolver}} has not been
> extended, that means if the same script is registered both via Resource
> Resolver and Bundle it seems that always the bundled one takes precedence.
> The default resolution order should be clarified in
> https://sling.apache.org/documentation/the-sling-engine/servlets.html#servlet-resolution-order.
> Also it should be possible to influence the order of precedence via OSGi
> configuration.
> In addition it should be clarified if embedded or precompiled scripts take
> preference
> (https://github.com/apache/sling-org-apache-sling-servlets-resolver#so-how-do-i-deploy-my-scripts).
> IMHO the resolution order is as follows
> 1. precompiled scripts
> 2. embedded scripts
> 3. resource resolver scripts
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
