You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2013/09/16 19:14:51 UTC
[jira] [Closed] (TAP5-2184) Select component fails validation due
to type mismatch when using model generated from String
[ https://issues.apache.org/jira/browse/TAP5-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-2184.
--------------------------------------
Resolution: Fixed
Fix Version/s: 5.4
> Select component fails validation due to type mismatch when using model generated from String
> ----------------------------------------------------------------------------------------------
>
> Key: TAP5-2184
> URL: https://issues.apache.org/jira/browse/TAP5-2184
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.4
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.4
>
>
> A recent change to the Select component enables, by default, the validation of a submitted value to a Select against its SelectModel.
> This works fine in most cases ... however, when the SelectModel is created from a String, the values are also Strings even if the property edited by the Select is a non-String type (relying, again, on TypeCoercer to convert). This causes a failure in the typical case where the string is a list of number, say "1,5,10"; the provided SelectModel provides the values as strings, e.g., "10", which does match against even a valid submitted value, since the ValueEncoder will have converted the value to a number before the search.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira