[
https://issues.apache.org/jira/browse/TAP5-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680025#action_12680025
]
Thiago H. de Paula Figueiredo commented on TAP5-565:
----------------------------------------------------
Ulrich: I agree with you, but how we could write a generic way to implement it?
The toClient() part is easy (toString()), but how to decode it? I guess we
could add ValueEncoders for Strings and number types, but not for arbitrary
classes.
> Add BeanPropertySelectModel
> ---------------------------
>
> Key: TAP5-565
> URL: https://issues.apache.org/jira/browse/TAP5-565
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.1.0.1
> Reporter: Kevin Menard
> Assignee: Kevin Menard
> Priority: Minor
>
> As raised in TAP5-213, we don't do enough to make the common cases of using
> the Select component easy enough. To this end, we should add back in the
> BeanPropertySelectModel default implementation like T4 had
> (http://tapestry.apache.org/tapestry4.1/apidocs/org/apache/tapestry/form/BeanPropertySelectionModel.html).
> Not only was it a good idea then, but it should help with a T4 migration to
> T5.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
