[
https://issues.apache.org/jira/browse/MYFACES-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Rinke updated MYFACES-1750:
----------------------------------
Status: Patch Available (was: Open)
> Evaluation of EL-Expression fails with custom PropertyResolver
> --------------------------------------------------------------
>
> Key: MYFACES-1750
> URL: https://issues.apache.org/jira/browse/MYFACES-1750
> Project: MyFaces Core
> Issue Type: Bug
> Components: General
> Affects Versions: 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.5
> Reporter: Stefan Rinke
> Priority: Critical
>
> When using a custom PropertyResolver in faces-config.xml like this:
> <application>
> <property-resolver>
> org.springframework.web.jsf.MessageSourcePropertyResolver
> </property-resolver>
> </application>
> the evaluation of an expression involving the PropertyResolver fails, when
> the expression appears on the right hand side. E.g. the expression #{
> bundle.test == 'xx' } succeeds, whereas #{ 'xx' == bundle.test } fails. In
> this example the property resolver is responsible for evaluating the 'test'
> property on the object 'bundle'.
> MyFaces has an expression factory which reassembles the expressions generated
> from the commons-el parser. This is done by replacing the so called
> 'suffixes' see org.apache.myfaces.el.ELParserHelper. The bug occurs when
> instances of BinaryOperatorExpression are handled, because myfaces only
> replaces the suffix of the first operand. This is why the first example works
> and the second fails.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
