[
https://issues.apache.org/jira/browse/SCXML-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13840064#comment-13840064
]
Ate Douma commented on SCXML-183:
---------------------------------
While looking into the current JexlEvaluator implementation, it turns out the
JexlEngine is a transient member, which thus might get 'lost' when the
JexlEvaluator instance is (de)serialized.
That makes exposing the engine, to support further customizations, less ideal,
as such customizations would get 'lost' as well.
Therefore I think it better to change this issue to only expose specific
JexlEngine settings, like strict/silent mode, and store these also in the
JexlEvaluator so they can be re-applied when after deserialization.
> Expose the underlying JexlEngine of JexlEvaluator to support like setting the
> engine to strict mode
> ---------------------------------------------------------------------------------------------------
>
> 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.
> 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.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
