[jira] [Updated] (JEXL-347) Missing unsolvable property exception for reference when used with equals
[
https://issues.apache.org/jira/browse/JEXL-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Biestro updated JEXL-347:
---
Affects Version/s: (was: 3.1)
> 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)
[jira] [Updated] (JEXL-347) Missing unsolvable property exception for reference when used with equals
[
https://issues.apache.org/jira/browse/JEXL-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Biestro updated JEXL-347:
---
Affects Version/s: 3.1
> 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
>Affects Versions: 3.1
>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)
[jira] [Updated] (JEXL-347) Missing unsolvable property exception for reference when used with equals
[
https://issues.apache.org/jira/browse/JEXL-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Biestro updated JEXL-347:
---
Fix Version/s: 3.2
> 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)
[jira] [Updated] (JEXL-347) Missing unsolvable property exception for reference when used with equals
[
https://issues.apache.org/jira/browse/JEXL-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Biestro updated JEXL-347:
---
Assignee: Henri Biestro
> 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
>
> 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)
