[ https://issues.apache.org/jira/browse/TAP5-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Denis Stepanov reopened TAP5-1445: ---------------------------------- yes, but you can't have a dynamic id - t:id="user_${user.id}" > Add clientId parameter to the Zone component > -------------------------------------------- > > Key: TAP5-1445 > URL: https://issues.apache.org/jira/browse/TAP5-1445 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core > Affects Versions: 5.2.4 > Reporter: Denis Stepanov > Assignee: Howard M. Lewis Ship > Priority: Minor > > It will solve dynamic zone id problem, when clientId is null it will use the > previous approach. Now we are forced to have a copy of the zone component > with a similar solution. > Also, it would be nice if a generated id is available before rendering, in a > case when someone calls getClient on a zone before it have been rendered. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira