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 2021/11/12 11:06:00 UTC

[jira] [Closed] (SLING-10862) Expose more details on servlet candidates in Servlet Resolver Web Console Plugin

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

Carsten Ziegeler closed SLING-10862.
------------------------------------

> Expose more details on servlet candidates in Servlet Resolver Web Console Plugin
> --------------------------------------------------------------------------------
>
>                 Key: SLING-10862
>                 URL: https://issues.apache.org/jira/browse/SLING-10862
>             Project: Sling
>          Issue Type: Improvement
>          Components: Servlets
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>            Priority: Major
>             Fix For: Servlets Resolver 2.9.0
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Currently the list of servlet candidates exposed via {{system/console/servletresolver}} look like this
> {code}
> /apps/.../base/components/page/page.html
> org.apache.sling.servlets.get.impl.DefaultGetServlet
> org.apache.sling.jcr.webdav.impl.servlets.SlingWebDavServlet
> {code}
> It would be nice to explicitly expose whether it is a resource script, bundled script (via proxy {{BundledScriptServlet}}) or regular servlet. For the latter two it would be nice to expose the exporting bundles as well (via {{Bundle b = FrameworkUtil.getBundle( servlet );}}.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)