How do I set a ui:table to Page 0 every time its rendered?

Question

Seems that the paging mechanism in my tables retain the page that
was last selected.
I would like them to always start at page 0.

Answer 1

This is the first difference, my Search page just
loads a data array and
puts that into Session so that the Master page can
display it after the use
selects a Search button, which takes them to the
Master page.Both your project and my project use the search page
to determine the subset of data to display. While we
do it differently, I do not think this interferes
with the table component's paging mechanism. To be
safe, when I have time, I will recreate with your
scenario, but I would be surprised if that made a
difference.
Are you trying to say that on the Search page I
should call the DataProvider
.cursorFirst() method? No,
If so that is not yet
available until I get to the Master
page.
age2 (master page)
o Add table bound to TRIP
o Modified trip row set's query to add querycriteria
for PERSONID
o Added button
o Prerender's code is
        try {
etSessionBean1().getTripRowSet().setObject(1,
(Object) getRequestBean1().getPersonId());
tripDataProvider.refresh();
tch (Exception e) {
log("cannot show trips");
ode]So on the Master page I have a ui:table with the
first column being a RadioButton that the user
selects. The user then selects a Detail button
to take them to the Detail page.
In the Master page's prerender method I've added
memberSummaryDataProvider.cursorFirst();
//memberSummaryDataProvider.refresh(); NO SUCH
METHOD
tableRowGroup1.setFirst(0);In your scenario, a call to setFirst(0) should not be
necessary. This is only necessary if you have the
search mechanism on the same page as the table. I
appologize for leading you down the wrong path. No problem.
>
You should be able to remove this.Done.
>
>
As I stated above nothing is preselected on the
Master page's ui:table.Same with mine
I go Search->Master (goto to Page3)->Detail->Search
(with different
search criteria which in turn generates adifferent
data array)->Master
(know the ui:table is at Page 3 and not at Page 1
which is the BUG.
Thanks you for your help. I just don't understandwhy
the ui:table is set
to Page 3 the second time I do a search.Me neither. On this page
(http://developers.sun.com/prodtech/javatools/jscreato
r/learning/tutorials/index.jsp) is a Creator docs
feedback alias. Perhaps you can zip up your project
(do a clean first) and send it to the alias with
"for chris" in the subject line.Thanks, unfortunately my project is already about 100 pages. It would
take me some time to trim it down to a minimum that you could look at.
>
>>
Perhaps I should be asking; What is thealternative
to refresh() for an
ObjectArrayDataProvider?You don't need it in your case.Understood.
Out of curiosity, does the ui:table use a VirtualForm that I'm not aware of?
If so what would that VirtualForms name be? I'm thinking of trying
to call discardSubmittedValues("virtualformname"). I've had some success
in solving other problems that are related to old values being retained
on other pages.
Just curious, and thanks for your help Chris.