[
https://issues.apache.org/jira/browse/TAPESTRY-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAPESTRY-2348.
------------------------------------------
Resolution: Invalid
Assignee: Howard M. Lewis Ship
On much later reflection, this is just too much magic for too little gain.
> Add annotation to expose the properties of a component field as properties
> of the component
> --------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-2348
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2348
> Project: Tapestry
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.0.11
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Priority: Minor
>
> This struck me as a useful idea, what if you could do the following:
> public class EditUser {
> @PropertyDelegate
> private User _user;
> ...
> }
> With this, all the properties of User would be properties of the EditUser
> page, with implementations delegating to the _user field.
> The annotation should include include and exclude attributes (comma separated
> list of property names) and should automatically exclude the "class"
> property.
> An advantage here is that you can take better advantage of the computed
> default for the value attribute of many components (i.e., matching a property
> of the component whose name matches the id).
> On the other hand, if there isn't a way to copy the annotations from the
> delegate object's getters and setters, this would likely cause more problems
> than it would solve.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
