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
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
