[jira] Updated: (TAP5-1008) MultiZoneUpdate.getZoneToRenderMap() should return a LinkedHashMap instead of an unordered HashMap

["Giulio Micali (JIRA)" <ji...@apache.org>]

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

Giulio Micali updated TAP5-1008:
--------------------------------

    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.


  was:
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" after, 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.



> MultiZoneUpdate.getZoneToRenderMap() should return a LinkedHashMap instead of an unordered HashMap
> --------------------------------------------------------------------------------------------------
>
>                 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
>
> 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.