[
https://issues.apache.org/jira/browse/JEXL-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732558#action_12732558
]
Henri Biestro commented on JEXL-11:
-----------------------------------
Fixed in 2.0 using the JexlEngine.setLenient(false) method.
> [jexl] Don't make null convertible into anything
> ------------------------------------------------
>
> Key: JEXL-11
> URL: https://issues.apache.org/jira/browse/JEXL-11
> Project: Commons JEXL
> Issue Type: Improvement
> Affects Versions: 1.0
> Environment: Operating System: other
> Platform: Other
> Reporter: Paul Libbrecht
> Priority: Minor
> Fix For: 2.0
>
>
> Currently JEXL is very tolerant with null (and unresolved variables)...
> I am unsure now but I think null will become false if the output of a test,
> null will become the empty
> string if concatenated to a string, null will become the number zero when
> added. Moreover,
> invoking a method on null gives you... null...
> I would love a switch that just disables all this (I think this would impact
> quite a lot) allowing my jexl
> snippets to be quite more predictable!
> paul
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
