1 Reply Latest reply on Sep 25, 2008 5:48 AM by Shervin Asgari

    rich:datascroller, request-scope data model and filtered tab

    Tony Gedge Newbie

      I have a data table with an attached scroller that is backed by a request-scope bean.

      The request scope bean extracts rows from a large database table. It has properties on the model that are used to restrict the rows shown - for example, only those rows which match a certain search criteria are shown.

      Everything works great except the data scroller. When a page is selected in the scroller the page displayed is always 1.

      From what I can see, the scroller's current page number is set during the apply request values phase. At this point in time, none of the model properties have been bound, so when the scroller asks the model for the row count, the size of the result set is unknown (the search criteria are unset) and the row count is zero. This means that the page will always be reset to 1.

      Is there a method to work around this behaviour?