You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Josh Canfield (JIRA)" <ji...@apache.org> on 2011/06/22 00:21:47 UTC

[jira] [Resolved] (TAP5-255) Easy management of zones inside a loop

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

Josh Canfield resolved TAP5-255.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 5.1.0.4

This has been fixed with the addition of the support for "id" in the zone component

An issue has been created to update the documentation.
https://issues.apache.org/jira/browse/TAP5-1552

> Easy management of zones inside a loop
> --------------------------------------
>
>                 Key: TAP5-255
>                 URL: https://issues.apache.org/jira/browse/TAP5-255
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>            Reporter: Stéphane Decleire
>             Fix For: 5.1.0.4
>
>         Attachments: ForceZoneId.java, Test.java, Test.tml, select.diff, zone.patch
>
>
> Enhancing the management of zones inside loops by removing the following zone limitation :
> "Unlike many other situations, Tapestry relies on you to specify useful and unique ids to Zone components, then reference those ids inside ActionLink components. 
> Using Zone components inside any kind of loop may cause additional problems, as Tapestry will uniqueify the client id you specify (appending an index number)."

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira