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

["Jochen Kemnade (JIRA)" <ji...@apache.org>]

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

Jochen Kemnade updated TAP5-1343:
---------------------------------

    Labels: bulk-close-candidate  (was: )

This issue has been last updated about 1.5 years ago, has no assignee, 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-6, 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.


> @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.2#6252)