[
https://issues.apache.org/jira/browse/DELTASPIKE-858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14363914#comment-14363914
]
Gerhard Petracek edited comment on DELTASPIKE-858 at 3/16/15 8:55 PM:
----------------------------------------------------------------------
we need to think about the supported syntax, because it isn't ambiguous once
you combine multiple expressions and you rely on the current behavior.
maybe we should provide multiple implementations of ExpressionInterpreter.
was (Author: gpetracek):
we need to think about the supported syntax, because it isn't ambiguous once
you combine multiple expressions and you rely on the current behavior.
> @Exclude usage of != operator in onExpression should match when the property
> is not defined
> -------------------------------------------------------------------------------------------
>
> Key: DELTASPIKE-858
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-858
> Project: DeltaSpike
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.3.0
> Environment: weld-se
> Reporter: Arrault
> Priority: Minor
> Attachments: ExcludeOnAbsentPropertyTest.java
>
>
> When using @Exclude(onExpression="property!=value"),
> I expect the bean to be excluded if the "property" is not defined which is
> not the case the current implementation
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
