I wonder if what zones to update could be determined by the server-side
by returning a Map<String,Block> or some such, instead of a plain Block.
But maybe you can leave the previous "zone" parameter behavior as is (
when link/form/select/etc expects to update a single predetermined zone ).
And add another mark parameter or mixing: "zones", that will then add
the proper javascript to support a map of zones/blocks returned by server..?
that way backward compatibility is still there.. and an added feature is
exposed for those that know about it and want to use it.
Howard M. Lewis Ship (JIRA) wrote:
[
https://issues.apache.org/jira/browse/TAP5-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship reassigned TAP5-108:
-----------------------------------------
Assignee: Howard M. Lewis Ship
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.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
