[jira] Assigned: (TAP5-243) Grid is too restrictive on when it initializes state

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

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

Howard M. Lewis Ship reassigned TAP5-243:
-----------------------------------------

    Assignee: Howard M. Lewis Ship

> Grid is too restrictive on when it initializes state
> ----------------------------------------------------
>
>                 Key: TAP5-243
>                 URL: https://issues.apache.org/jira/browse/TAP5-243
>             Project: Tapestry 5
>          Issue Type: Bug
>            Reporter: Dan Adams
>            Assignee: Howard M. Lewis Ship
>
> We have a component which exports data from a grid in CSV format. When we upgrade to 5.0.15 it broke because Grid doesn't initialize the SortModel until setupRender. This means that you can't get sorting information from a Grid if an event handler or if your component that references the Grid comes before it in the rendering/form processing.
> One solution is to push the SortModel into to page but 1) the default implementation is part of the Grid and 2) this would be really gross and non-usable because the state information behind the default sort model is persisted in Grid (so the page would have to take care of this manually in each instance).
> Another option would be to use @Cached on the getters for state-related stuff so that no matter when it gets called it's always lazy initialized, it's only initialized once, and it's always correct.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org