[jira] Commented: (TOMAHAWK-538) dataScoller displays wrong page after increasing row count on dataTable resulting in page count which is smaller than last displayed page.

["Torsten Krah (JIRA)" <de...@myfaces.apache.org>]

    [ https://issues.apache.org/jira/browse/TOMAHAWK-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487582 ] 

Torsten Krah commented on TOMAHAWK-538:
---------------------------------------

Ok i got some workaround to solve this problem.

Analyzing the flow i would think this happens:

The state of the UIData gets restored and the old first value is used to render the table rows instead of the new correct value. (need to anlalyze a bit more to get it).
My workaround for now:

I do a binding of the dataTable, the UIData component in my bean ( theTable).
Registered a valueChangeListener and if the event happens i call:

theTable.setFirst((Integer) event.getNewValue());

The Table and the DataScroller works without any additional patches from above than.

Torsten


> dataScoller displays wrong page after increasing row count on dataTable resulting in page count which is smaller than last displayed page.
> ------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TOMAHAWK-538
>                 URL: https://issues.apache.org/jira/browse/TOMAHAWK-538
>             Project: MyFaces Tomahawk
>          Issue Type: Bug
>          Components: Data Scroller
>    Affects Versions: 1.1.3
>         Environment: Tomcat 5.5, myfaces 1.1.3 and tomahawk 1.1.3, java 1.5
>            Reporter: Torsten Krah
>
> Using a dataScoller to navigate through the extended dataTable with dynamically changable row Count doesnt work in all combinations.
> Take this example:
> You got a table, initially set to 10 rows and have 20 data sets to display.
> You get 2 pages in scroller with 10 rows each page.
> Now change row Count to 15.
> You get 2 pages, page one with 15 rows, page 2 with 5.
> Now change to page 2 - important!
> And now change the row Count to 20. 
> You should get only one page with 20 rows now - but the scoller still shows the last 5 rows displayed and gets not updated correctly like it should be.
> It also shows still this ( printed some informations for the backing bean values ):
> 20 Customers found, 5 Customers showing , from 16 up to 20. Page 2 / 1	
> It shows Page 2 of 1 - but it should be 1 of 1, the scroller gets not updated right, if the page count gets smaller than the last displayed one.
> kind regards
> Torsten

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