[
https://issues.apache.org/jira/browse/SLING-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15938181#comment-15938181
]
Radu Cotescu edited comment on SLING-6637 at 3/23/17 12:18 PM:
---------------------------------------------------------------
I tend to agree with Robert's view here: why do we want to move
{{data-sly-use}} errors in the log only? Given the construct, I think that
{{data-sly-use}} plays an important role in a script, therefore it shouldn't
fail silently...
was (Author: radu.cotescu):
I tend to agree with Robert's view here: why do we want to move
{{data-sly-use}} errors in the log only? Given the construct, I think that
{{data-sly-use}} plays an important role in a script, therefore it should fail
silently...
> [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)
