[
https://issues.apache.org/jira/browse/SLING-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936768#comment-14936768
]
Radu Cotescu commented on SLING-4442:
-------------------------------------
I've removed {{data-sly-resource}} from this issue since this block element can
also be used to include {{SyntheticResources}}, and the block element correctly
bubbles the errors it receives down the stream from the {{RequestDispatcher}}.
> Invalid parametrization of Sightly statements should lead to exceptions
> instead of errors
> -----------------------------------------------------------------------------------------
>
> Key: SLING-4442
> URL: https://issues.apache.org/jira/browse/SLING-4442
> Project: Sling
> Issue Type: Improvement
> Components: Scripting
> Affects Versions: Scripting Sightly Engine 1.0.0
> Reporter: Konrad Windszus
> Assignee: Radu Cotescu
> Fix For: Scripting Sightly Engine 1.0.6
>
>
> Currently invalid parametrization of Sightly statements only leads to
> errors/warnings in the log. Rather programmatic errors should lead to
> exceptions so that errors are detected earlier during development and to
> prevent invalid HTML output due to failures within a Sightly script (a HTML
> page with a 500 status is the right thing to do IMHO).
> This affects:
> # data-sly-include with invalid/empty path
> # data-sly-call with invalid name (this does not even provide logging
> currently)
> # data-sly-use when the identifier cannot be solved by any of the registered
> {{UseProvider}} services
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
