[jira] [Resolved] (SLING-8991) Avoid recreation of main servlet on config change

["Carsten Ziegeler (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-8991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-8991.
-------------------------------------
    Resolution: Fixed

Updated in rev dd431d8. The configuration can simply be updated when getting a modified event. The only exception is the rare case where a custom servlet name is specified. In this case the servlet needs to be re-registered with the http whiteboard. But we can do this without tearing down any other registration, minimizing the impact

> Avoid recreation of main servlet on config change
> -------------------------------------------------
>
>                 Key: SLING-8991
>                 URL: https://issues.apache.org/jira/browse/SLING-8991
>             Project: Sling
>          Issue Type: Improvement
>          Components: Engine
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>            Priority: Major
>             Fix For: Engine 2.6.24
>
>
> If the main servlet is reconfigured, it is deactivated and then activated again with the new configuration. This creates unnecessary churn in the system as this affects a couple of services beeing re-registered.
> We can avoid this and handle the reconfiguration within the implementation



--
This message was sent by Atlassian Jira
(v8.3.4#803005)