I was hoping you would not notice that :-)
-bd-
On Sep 27, 2005, at 4:41 PM, sean schofield (JIRA) wrote:
[ http://issues.apache.org/jira/browse/MYFACES-623?
page=comments#action_12330649 ]
sean schofield commented on MYFACES-623:
----------------------------------------
Yes your new test case seems to do the trick. The problem with the
original was that you were comparing the int value of the Integer
you just created to 14. You weren't checking the actual result of
the getValue.
setValue() method of ValueBindingImpl does not behave properly
--------------------------------------------------------------
Key: MYFACES-623
URL: http://issues.apache.org/jira/browse/MYFACES-623
Project: MyFaces
Type: Bug
Components: JSR-127
Versions: 1.1.0
Reporter: sean schofield
Attachments: MYFACES-623.patch
According to section 5.1.4 of the specification (p. 5-4) ...
If you have #{expr-a[value-b]} where value-a is a Map then ...
call value-a.put(value-b, newValue).
The MyFaces implementation is coercing newValue into String which
is incorrect behavior.
NOTE: I discovered the problem while using a bean that was
programatically added to the session map. So there is is no class
defined in faces-config.xml. I don't think this should matter but
I thought I would mention it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the
administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
