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

Ate Douma updated SCXML-183:
----------------------------

    Description: 
Currently the JexlEvaluator creates the JexlEngine with mostly default settings.
The JexlEvaluator class can be extended to override the createEngine method and 
thus allows custom configurations, but this is less convenient.
Especially the JexlEngine strict/silent mode settings are important with regard 
to its internal behavior.
By exposing these settings through the JexlEvaluator it no longer is needed to 
extend to control these settings.

  was:
Currently the JexlEvaluator creates the JexlEngine with mostly default settings.
The JexlEvaluator class can be extended to override the createEngine method and 
thus allows custom configurations, but this is less convenient.
By exposing the JexlEngine through a getEngine() method, this will be much 
easier.
Note: the JexlEvaluator is exposed within SCXML only through its Evaluator 
interface, so this getEngine() method is typically only exposed  and needed at 
instantiation time. 


> Expose JexlEngine strict/silent mode settings  through the JexlEvaluator for 
> easier customization
> -------------------------------------------------------------------------------------------------
>
>                 Key: SCXML-183
>                 URL: https://issues.apache.org/jira/browse/SCXML-183
>             Project: Commons SCXML
>          Issue Type: Improvement
>    Affects Versions: 2.0
>            Reporter: Ate Douma
>            Assignee: Ate Douma
>             Fix For: 2.0
>
>
> Currently the JexlEvaluator creates the JexlEngine with mostly default 
> settings.
> The JexlEvaluator class can be extended to override the createEngine method 
> and thus allows custom configurations, but this is less convenient.
> Especially the JexlEngine strict/silent mode settings are important with 
> regard to its internal behavior.
> By exposing these settings through the JexlEvaluator it no longer is needed 
> to extend to control these settings.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to