You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2017/04/26 12:17:04 UTC

[jira] [Resolved] (SLING-6796) Servlet Resolver Test: Warn about non-existing resources

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

Konrad Windszus resolved SLING-6796.
------------------------------------
       Resolution: Fixed
    Fix Version/s: Servlets Resolver 2.4.12

Fixed in [r1792739|https://svn.apache.org/r1792739].

> Servlet Resolver Test: Warn about non-existing resources
> --------------------------------------------------------
>
>                 Key: SLING-6796
>                 URL: https://issues.apache.org/jira/browse/SLING-6796
>             Project: Sling
>          Issue Type: Improvement
>          Components: Servlets
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>             Fix For: Servlets Resolver 2.4.12
>
>
> Currently the servlet resolver test at /system/console/servletresolver does not emit a warning if a path to a non-existing resource is given. Since that always leads to falling back to the default GET servlet there should be a dedicated warning, in case the resource could not be found.
> This would have helped also for issues like SLING-6791.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)