[MYFACES-1750] Evaluation of EL-Expression fails with custom PropertyResolver

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.5, 1.1.6-SNAPSHOT, 1.1.6
• Fix Version/s: 1.1.6
• Component/s: General
• Assignee: Leonardo Uribe
• Reporter: Stefan Rinke
• Created: 23/Oct/07 09:22
• Updated: 12/Aug/08 21:03
• Resolved: 09/Apr/08 21:57

Description

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.