[
https://issues.apache.org/jira/browse/TAP5-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giulio Micali updated TAP5-255:
-------------------------------
Attachment: ForceZoneId.java
zone.patch
the previous patch attacched had a bug with AjaxFormLoop.
Added an example of forcing clientId: ForceZoneId.java
> 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
> Attachments: ForceZoneId.java, select.diff, Test.java, Test.tml,
> 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.
-
You can reply to this email to add a comment to the issue online.
