You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2016/02/22 14:45:20 UTC

[jira] [Updated] (TAP5-1399) Replace base class behavior for fields with meta-programming via annotations

     [ https://issues.apache.org/jira/browse/TAP5-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jochen Kemnade updated TAP5-1399:
---------------------------------
    Labels: bulk-close-candidate  (was: )

This issue 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 version of Tapestry (currently 5.4.0, available from Maven Central), please update it as soon as possible and add '5.4.0') to the issue's affected versions.

> Replace base class behavior for fields with meta-programming via annotations
> ----------------------------------------------------------------------------
>
>                 Key: TAP5-1399
>                 URL: https://issues.apache.org/jira/browse/TAP5-1399
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.3
>            Reporter: Howard M. Lewis Ship
>            Priority: Minor
>              Labels: bulk-close-candidate
>
> Not quite sure what this would look like, but it would be very cool if there was a more meta-programming way to build new types of form control components (TextField and friends) that was based on annotations and not on knowing how to subclass the existing tree of implementations.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)