[ http://issues.apache.org/jira/browse/MYFACES-623?page=comments#action_12331125 ]
Bill Dudney commented on MYFACES-623: ------------------------------------- Hi Oliver, I like the idea of moving the fix to ValueBindingImpl.setValue() but I'm not sure that removing the coercion is the right thing. Will there ever be a case where the converter is not invoked but coercion should happen? If so I think removing this will cause reflection exceptions on invocation of the set method. I guess we could then go fix where/when the converter is not being called. Thoughts? > 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
