You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Karl Pauls (JIRA)" <ji...@apache.org> on 2019/05/06 10:46:00 UTC

[jira] [Updated] (SLING-8327) Expose resource path in WebConsole for "Sling Servlet Resolver"

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

Karl Pauls updated SLING-8327:
------------------------------
    Fix Version/s:     (was: Servlets Resolver 2.5.4)
                   Servlets Resolver 2.5.6

> Expose resource path in WebConsole for "Sling Servlet Resolver"
> ---------------------------------------------------------------
>
>                 Key: SLING-8327
>                 URL: https://issues.apache.org/jira/browse/SLING-8327
>             Project: Sling
>          Issue Type: Improvement
>          Components: Servlets
>    Affects Versions: Servlets Resolver 2.5.2
>            Reporter: Konrad Windszus
>            Priority: Major
>             Fix For: Servlets Resolver 2.5.6
>
>         Attachments: Screenshot 2019-03-25 at 13.58.21.png
>
>
> As the resource path very often cannot be easily derived from the request path (due to mapping and sling:alias) it would be helpful to expose in the web console at {{/system/console/servletresolver}} not only the decomposed URL parts but also the resolved underlying resource path (similar to what is exposed at {{/system/console/jcrresolver}}).



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