[ 
https://issues.apache.org/jira/browse/SLING-11578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17640093#comment-17640093
 ] 

Oliver Lietz commented on SLING-11578:
--------------------------------------

[~cziegeler], "start": having all dependencies resolved and Sling Engine 
("Core") bundle in status {{{}ACTIVE{}}}. That was a good checkpoint in the 
past. In unusual or testing setups Sling Servlets Resolver is not required, but 
I see your point. I will try to break down the {{sling}} feature further into 
smaller chunks.

In *my* view (using Sling also outside of AEM) Sling's core is Sling Resource 
API with Sling's HTTP API sitting on top. And in *my* view having HTTP Servlets 
API leaked into Sling API is a design flaw as it makes using a different HTTP 
API/model unnecessary tricky.

> 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)

Reply via email to