[jira] [Resolved] (SLING-4442) Invalid parametrisation of Sightly statements should lead to exceptions instead of errors

["Radu Cotescu (JIRA)" <ji...@apache.org>]

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

Radu Cotescu resolved SLING-4442.
---------------------------------
    Resolution: Fixed

Fixed in [r1706441|https://svn.apache.org/viewvc?view=revision&revision=r1706441].

> Invalid parametrisation 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)