[
https://issues.apache.org/jira/browse/JEXL-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rahul Akolkar resolved JEXL-11.
-------------------------------
Resolution: Fixed
This should be fixed in the 2.0 branch in SVN. Please try it out (by building
the branch) and if further work is needed, reopen this issue with a complete
JUnit test that fails.
> [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.
