[
https://issues.apache.org/jira/browse/TAP5-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679762#action_12679762
]
Howard M. Lewis Ship commented on TAP5-108:
-------------------------------------------
Thiago -- we are thinking alike; the new behavior is triggered by a return type
of MultiZoneUpdate (which is kind of like a typed Map of string and
Renderable/Block/RenderCommand/whatever).
> ActionLink should be able to update several zones
> -------------------------------------------------
>
> Key: TAP5-108
> URL: https://issues.apache.org/jira/browse/TAP5-108
> Project: Tapestry 5
> Issue Type: Improvement
> Affects Versions: 5.0.15
> Reporter: Igor Drobiazko
> Assignee: Howard M. Lewis Ship
>
> Unfortunately the ActionLink's parameter "zone" expect a single zone.
> Commonly, we want to update several parts of the client. It would be very
> nice to be able to update a bunch of zones after an action was triggered.
> This limitation is quite frustrating for people coming from T4 because
> "updateComponents" expected a list of component ids.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
