[ http://issues.apache.org/jira/browse/TAPESTRY-747?page=comments#action_12459133 ] Ron Piterman commented on TAPESTRY-747: ---------------------------------------
So now the bug is fixed, but after reading the comment I don't know if it is fixed or not, was a translator added? there are no commits on the issue. Anyway, the value of the Select is not an index, but a String - which the application may interpret as it wants. To make the "interpretation" much easier, one could use a translator- quite straightfarword then... when reading the value, reading an arbitrary object and formatting it to a string with the translator. When writing the object, using the tarnslator to parse the string and writing an arbitrary object. > Add translator parameter to the Select component > ------------------------------------------------ > > Key: TAPESTRY-747 > URL: http://issues.apache.org/jira/browse/TAPESTRY-747 > Project: Tapestry > Issue Type: Improvement > Components: Framework > Affects Versions: 4.0 > Reporter: Ron Piterman > Priority: Minor > Fix For: 4.1.1 > > > Although most cases will use a PropertySelection, since under the hood the > Select component is de facto a string based input, just like TextField or > -Area, a translator parameter should be added. -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
