You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2018/11/09 07:27:00 UTC

[jira] [Resolved] (SLING-5004) Improve servlet tracking by using filter

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

Carsten Ziegeler resolved SLING-5004.
-------------------------------------
    Resolution: Duplicate

This has already been implemented

> Improve servlet tracking by using filter
> ----------------------------------------
>
>                 Key: SLING-5004
>                 URL: https://issues.apache.org/jira/browse/SLING-5004
>             Project: Sling
>          Issue Type: Improvement
>          Components: Servlets
>            Reporter: Carsten Ziegeler
>            Priority: Major
>
> Right now, the servlet resolver is tracking all servlets, examinging their service properties and then decides whether to use the servlet.
> If we create a filter expression when tracking the servlets, only servlets for the servlet resolver will be pushed into the service. The benefit of this is that we can change the bindServlet method to get the Servlet instance. This will simplify the current rather complex handling/syncing.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)