[TAP5-1008] The order in which zones are added to the MultiZoneUpdate should be honored on the client side, to allow nested zones to be updated all in a single request

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 5.1.0.1
• Fix Version/s: 5.4
• Component/s: tapestry-core
• Assignee: Howard Lewis Ship
• Reporter: Giulio Micali
• Created: 06/Feb/10 07:51
• Updated: 10/Jan/13 03:29
• Resolved: 10/Jan/13 03:29

Description

In this way, the developer can choose the order in which the zones are rendered:
this can be useful when a component rendering phase creates a rendering variable or stores values in request/session attributes, and the last zone uses them to render itself.

TODO:
Actually, the above method store the "child" in the map before the "parent" , so the map will be filled in a stack-like order, and the MultiZoneUpdateEventResultProcessor will render in that order.
The return order(and eventually if the MultiZoneUpdateEventResultProcessor will revert it) must be choosen by tapestry developers and clearly defined in documentation.