[jira] [Resolved] (SLING-10554) The check for valid requests should not fail on a resolution path that is null

["Karl Pauls (Jira)" <ji...@apache.org>]

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

Karl Pauls resolved SLING-10554.
--------------------------------
    Resolution: Fixed

Done in https://github.com/apache/sling-org-apache-sling-engine/pull/16

> The check for valid requests should not fail on a resolution path that is null
> ------------------------------------------------------------------------------
>
>                 Key: SLING-10554
>                 URL: https://issues.apache.org/jira/browse/SLING-10554
>             Project: Sling
>          Issue Type: Improvement
>          Components: Engine
>    Affects Versions: Engine 2.7.6
>            Reporter: Karl Pauls
>            Assignee: Karl Pauls
>            Priority: Major
>             Fix For: Engine 2.7.8
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The isValidRequest check (see SLING-10225) uses {{getResourceMetadata().getResolutionPath();}} which is taken from the resource metadata. While a custom resource should have correct metadata that is not always the case which can cause the resolution patch to be null.
> The check should take that into account.



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