[jira] [Updated] (SLING-4442) Invalid parametrization of Sightly statements should lead to exceptions instead of errors
[
https://issues.apache.org/jira/browse/SLING-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu updated SLING-4442:
Description:
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
was:
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-resource with a path that doesn't solve to an existing resource
# 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
> 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)
[jira] [Updated] (SLING-4442) Invalid parametrization of Sightly statements should lead to exceptions instead of errors
[
https://issues.apache.org/jira/browse/SLING-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu updated SLING-4442:
Description:
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-resource with a path that doesn't solve to an existing resource
# 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
was:
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 e.g.
# data-sly-include with invalid/empty path
# data-sly-resource with empty path
# data-sly-call with invalid name (this does not even provide logging currently)
> 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-resource with a path that doesn't solve to an existing resource
> # 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)
[jira] [Updated] (SLING-4442) Invalid parametrization of Sightly statements should lead to exceptions instead of errors
[ https://issues.apache.org/jira/browse/SLING-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-4442: Fix Version/s: Scripting Sightly Engine 1.0.6 > 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 > 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 e.g. > # data-sly-include with invalid/empty path > # data-sly-resource with empty path > # data-sly-call with invalid name (this does not even provide logging > currently) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4442) Invalid parametrization of Sightly statements should lead to exceptions instead of errors
[ https://issues.apache.org/jira/browse/SLING-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-4442: --- Component/s: Scripting > 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 > > 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 e.g. > # data-sly-include with invalid/empty path > # data-sly-resource with empty path > # data-sly-call with invalid name (this does not even provide logging > currently) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
