You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Henri Biestro (JIRA)" <ji...@apache.org> on 2016/08/03 16:13:20 UTC

[jira] [Commented] (JEXL-210) The way to cancel script execution with an error

    [ https://issues.apache.org/jira/browse/JEXL-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15406138#comment-15406138 ] 

Henri Biestro commented on JEXL-210:
------------------------------------

I dont understand; isn't the current behavior the logical outcome of JEXL-207 ? If you want the script to stop on error, set the engine as strict & !silent.
You want the engine to make a difference between an error (property, method, etc) and an exception ?

> The way to cancel script execution with an error
> ------------------------------------------------
>
>                 Key: JEXL-210
>                 URL: https://issues.apache.org/jira/browse/JEXL-210
>             Project: Commons JEXL
>          Issue Type: New Feature
>    Affects Versions: 3.0
>            Reporter: Dmitri Blinov
>            Assignee: Henri Biestro
>            Priority: Minor
>
> I don't see a way now to cancel script execution with some kind of error. Unfortunately it's not possible to just throw an exception from some method as this will rely on current settings of context/engine *strictness* and *verboseness*. Using InterruptedException for this purpose is not an option because I think it has special meaning of cancelling the current thread execution. Yet the task I beleive is quite common - to inform the executing environment that the script has encountered some unavoidable situation and can not continue. Just like *return* statement but returning not a value but an error. 
> For this purpose we can simply introduce some new type of exception, for example 
> {code}
>     public static class Error extends JexlException {
>     ...
> {code}
> and by throwing it from any method the JexlEngine will terminate the current script execution regardless of strictness/verboseness. May be this task even deserves to have a special operator, for example 
> {code}
> raise 'Something has happended';
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)