You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Kalle Korhonen (JIRA)" <ji...@apache.org> on 2015/03/06 08:01:38 UTC

[jira] [Resolved] (TAP5-2462) Parent component should be able to reset a Grid regardless of its internal state

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

Kalle Korhonen resolved TAP5-2462.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 5.4

> Parent component should be able to reset a Grid regardless of its internal state
> --------------------------------------------------------------------------------
>
>                 Key: TAP5-2462
>                 URL: https://issues.apache.org/jira/browse/TAP5-2462
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.4
>            Reporter: Kalle Korhonen
>            Assignee: Kalle Korhonen
>             Fix For: 5.4
>
>
> Calling Grid.reset() from the parent component may result in NullPointerException:
> Caused by: java.lang.NullPointerException
> at org.apache.tapestry5.corelib.components.Grid.setCurrentPage(Grid.java:600)
> at org.apache.tapestry5.corelib.components.Grid.reset(Grid.java:636)
> at org.tynamo.examples.simple.pages.List.resetGrid(List.java:83)
> at org.tynamo.examples.simple.pages.List.setupRender(List.java)
> The issue is that setCurrentPage(1) on Grid.reset() is really unnecessary or at least should be after sortModel.clear(); (lines 636-637)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)