tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] Created: (TAP5-1343) @Clientid field annotation: supplies logic to set fields value in setup render phase, expose it as property by implementing ClientIdElement
Date Wed, 10 Nov 2010 23:30:14 GMT
@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.3
            Reporter: Howard M. Lewis Ship
            Priority: Minor


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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message