[ http://issues.apache.org/jira/browse/MYFACES-736?page=comments#action_12356903 ]
Oliver Rossmueller commented on MYFACES-736: -------------------------------------------- As Martin pointed out there was a reason why coercion was removed in ValueBindingImpl.setValue: it is against the spec and therefore breaks the TCK. So I'm sorry but from my POV it is not possible to revert the ValueBindingImpl.setValue patch (2.10.2005). From the comments above I suppose the problem is more related to converters as in the exmple mentioned a short is required but the value is converted to long. It might be possible that the converter implementations rely on the coercion that was done by ValueBindingImpl and which is gone now. > Number converter not working with Number > ---------------------------------------- > > Key: MYFACES-736 > URL: http://issues.apache.org/jira/browse/MYFACES-736 > Project: MyFaces > Type: Bug > Components: Implementation > Versions: Nightly > Reporter: Sylvain Vieujot > > If the backing bean setter takes a Number argument (Integer, Float, ...), the > converter fails : > Conversion Error "XXX: Error during model data update. > If the setter uses a primitive type, then it works fine. > This worked with the trunk version from September 30. > There must have been a change that broke it since. -- 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
