[
https://issues.apache.org/jira/browse/TAP5-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14713011#comment-14713011
]
Thiago H. de Paula Figueiredo commented on TAP5-565:
----------------------------------------------------
Since Tapestry 5.2 we have SelectModelFactory, which provides the creation of
SelectModel based on property names, so I believe this was already implemented
and I'll close it as such.
[1]
http://tapestry.apache.org/5.3/apidocs/org/apache/tapestry5/services/SelectModelFactory.html
> 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
> Labels: bulk-close-candidate
> Fix For: 5.2
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
