[
https://issues.apache.org/jira/browse/SLING-11578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-11578.
--------------------------------------
Resolution: Fixed
Further entangled the component dependencies in:
https://github.com/apache/sling-org-apache-sling-engine/commit/113cd7718f2ed1bf12549298ba8836871930bbd9
The request processor is now a separate DS component which configures the
processing (previously done by SlingMainServlet). This allows to use the
processor even if the main servlet is not registered.
Moved nearly all services to DS managed services. There are two exceptions :the
ServletContext and the main servlet registered as both of them have dynamic
properties/values which need to be available/calculated first.
> Make authenticator and servlets resovler required for main servlet
> ------------------------------------------------------------------
>
> Key: SLING-11578
> URL: https://issues.apache.org/jira/browse/SLING-11578
> Project: Sling
> Issue Type: Improvement
> Components: Engine
> Affects Versions: Engine 2.11.0
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: Engine 2.12.0
>
>
> We currently have some strange code: the sling main servlet is available
> immediately but then registers parts of the functionality only once the
> authenticator and servlets resolver are available. And then there is code
> here and there checking if those services are really available.
> We can probably simplify this a lot of we make the required
> services...required and let DS handle it
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
