[
https://issues.apache.org/jira/browse/SLING-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15938154#comment-15938154
]
Konrad Windszus edited comment on SLING-6637 at 3/23/17 11:52 AM:
------------------------------------------------------------------
bq. I like to reopen this issue, and like to see if we can log these exceptions
(warn or error).
That should IMHO happen already. But the important part is that the exception
thrown and therefore is by default visible in the script as well. You could for
example also catch that exception in a servlet filter, if you don't want the
exception to be exposed.
was (Author: kwin):
bq. I like to reopen this issue, and like to see if we can log these exceptions
(warn or error).
That should IMHO happen already. But the important part is that the exception
thrown and therefore by default visible in the script as well. You could for
example also catch that exception in a servlet filter, if you don't want the
exception to be exposed.
> [htl] data-sly-use should not raise an exception when resource doesn't exist
> ----------------------------------------------------------------------------
>
> Key: SLING-6637
> URL: https://issues.apache.org/jira/browse/SLING-6637
> Project: Sling
> Issue Type: Bug
> Components: Scripting
> Reporter: Feike Visser
> Assignee: Radu Cotescu
>
> Following code:
> {code}
> <sly data-sly-use.x="${ 'x/y/z' }"/>
> {code}
> You get now the following exception:
> {code}
> org.apache.sling.scripting.sightly.SightlyException: No use provider could
> resolve identifier x/y/z
> {code}
> In practice you want to have a null-value assigned to x, now developers will
> make a lot of checks to make sure the resource does exist.
> In addition we can log warning message when this happens.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
