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 2015/01/12 09:10:47 UTC

[jira] [Closed] (TAP5-1343) @Clientid field annotation: supplies logic to set fields value in setup render phase, expose it as property by implementing ClientIdElement

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

Jochen Kemnade closed TAP5-1343.
--------------------------------
    Resolution: Invalid

We assume this is no longer relevant and therefore close it.
If you still have this issue in a recent Tapestry version (such as 5.3.8 or the latest 5.4 preview release), feel free to provide the necessary information and reopen.

> @Clientid field annotation: supplies logic to set fields value in setup render phase, expose it as property by implementing ClientIdElement
> -------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1343
>                 URL: https://issues.apache.org/jira/browse/TAP5-1343
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.2
>            Reporter: Howard M. Lewis Ship
>            Priority: Minor
>              Labels: bulk-close-candidate
>
> I see an awful lot of similar code for making a component maintain a client id.  A simple annotation for that would be great:
> The field becomes read-only
> The fields value is set in setupRender phase
> The class automatically implements ClientElement
> The class gets an implementation of getClientId() that returns the allocated client id



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