[jira] [Comment Edited] (JEXL-347) Missing unsolvable property exception for reference when used with equals

["Henri Biestro (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JEXL-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354603#comment-17354603 ] 

Henri Biestro edited comment on JEXL-347 at 5/31/21, 5:47 PM:
--------------------------------------------------------------

Mixed up 2 bug fixes at commit, should have stashed...

https://github.com/apache/commons-jexl/commit/cc963c93c1ded0238f1cb53cea69cfc0fd659b9c

https://github.com/apache/commons-jexl/commit/438bc977beecf51f922f5e02a7dac630911a511d


was (Author: henrib):
https://github.com/apache/commons-jexl/commit/cc963c93c1ded0238f1cb53cea69cfc0fd659b9c

> 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
>            Assignee: Henri Biestro
>            Priority: Minor
>             Fix For: 3.2
>
>
> 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)