You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Bernd Bohmann (JIRA)" <de...@myfaces.apache.org> on 2007/05/16 22:36:16 UTC

[jira] Resolved: (TOBAGO-399) ColumnSelector / SheetState with null-outcome

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

Bernd Bohmann resolved TOBAGO-399.
----------------------------------

    Resolution: Fixed

> ColumnSelector / SheetState with null-outcome
> ---------------------------------------------
>
>                 Key: TOBAGO-399
>                 URL: https://issues.apache.org/jira/browse/TOBAGO-399
>             Project: MyFaces Tobago
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0.10
>            Reporter: Matthias Wronka
>         Assigned To: Bernd Bohmann
>            Priority: Minor
>             Fix For: 1.0.11
>
>
> In a table with a columnselector-tag we can delete rows. In the corresponding action-method we update our model and call SheetState.resetSelected(). Everything works fine, if the action-method has a non-null outcome and there is a corresponding navigation-rule. If the action-method has a null-outcome the page is reloaded and the previously deleted row is missing as expected. But in our example the first row is selected (ignoring the fact that we have reseted the SheetState). If you ommit the columnselector-tag everything works fine again (also with the null-outcome).

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