[ http://issues.apache.org/jira/browse/MYFACES-623?page=comments#action_12331161 ]
Oliver Rossmueller commented on MYFACES-623: -------------------------------------------- Hi Bill, I checked the spec document and there is no word about coercion in the 5.1.4 Set Value Semantics section. I also had a look at the RI sources and there is no coercion in ValueBindingImpl.setValue, either. So I suppose it's save to remove coercion in MyFaces' ValueBindingImpl, too. From my POV it's even required to do so to comply with the spec. In my interpretion of the spec it's up to the application developer to provide a converter where necessary, but it's not required for the JSF runtime to try to guess the right conversion to match UI and model. > 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 > Assignee: Oliver Rossmueller > Fix For: 1.1.1 > 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
