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 2015/08/12 09:45:45 UTC

[jira] [Created] (SLING-4942) Modified behaviour of data-sly-resource

Konrad Windszus created SLING-4942:
--------------------------------------

             Summary: Modified behaviour of data-sly-resource
                 Key: SLING-4942
                 URL: https://issues.apache.org/jira/browse/SLING-4942
             Project: Sling
          Issue Type: Bug
          Components: Scripting
    Affects Versions: Scripting Sightly Engine 1.0.2
            Reporter: Konrad Windszus


In previous versions of sightly (i.e. part of AEM 6.0) {{data-sly-resource}} was  not emitting a failure in case a non-existing resource path was referenced. Instead it just skipped that Sightly block. With the Sightly implementation from Sling this leads to an exception ({{javax.servlet.ServletException: org.apache.sling.api.resource.ResourceNotFoundException: No resource found}}).
There is a difference though if data-sly-resource is also used with the option resourceType. In that case it will work perfectly fine on the non-existing resource.
Please clarify what is the desired behaviour.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)