Cameron Samak created JEXL-347:
----------------------------------
Summary: Missing unsolvable property exception for reference when
used with equals
Key: JEXL-347
URL: https://issues.apache.org/jira/browse/JEXL-347
Project: Commons JEXL
Issue Type: Bug
Reporter: Cameron Samak
I expected {code}A.B == 5{code} (with a strict engine and with nothing in the
context) to result in an unsolvable property exception, but instead the result
was false.
I hit this as part of an attempt to upgrade from 3.0 to a recent snapshot. I
think the change in behavior may be related to the addition of ASTEQNode and
ASTNENode to isTernaryProtected?
Is it intentional that equal and not equal are handled this way when e.g.
greater than or less than are not? If so, is there any option flag that can
restore the behavior?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
