[jira] Updated: (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

["Howard M. Lewis Ship (JIRA)" <ji...@apache.org>]

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

Howard M. Lewis Ship updated TAP5-1008:
---------------------------------------

     Summary: 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  (was: MultiZoneUpdate.getZoneToRenderMap() should return a LinkedHashMap instead of an unordered HashMap)
    Priority: Minor  (was: Major)

There's a number of work arounds, such as using ProgressiveDisplay components or equivalent ad-hoc JavaScript, but all of those do require additional requests.

> 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
> -----------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1008
>                 URL: https://issues.apache.org/jira/browse/TAP5-1008
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.1.0.1
>            Reporter: Giulio Micali
>            Priority: Minor
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.