[ https://issues.apache.org/jira/browse/TAP5-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Kemnade updated TAP5-565:
--------------------------------
Labels: bulk-close-candidate (was: )
This issue has been last updated more than a year ago, affects an old version of Tapestry
that is not actively developed anymore, and is therefore prone to be bulk-closed in the near
future.
If the issue still persists with the most recent development preview of Tapestry (5.4-beta-35,
which is available from Maven Central), please update it as soon as possible. In the case
of a feature request, please discuss it with the Tapestry developer community on the dev@tapestry.apache.org
mailing list first.
> 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
>
> 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)
|