A valued customer asks:
There are two main keys to this technique. The first is to not expire the managed bean of the view with the pageFlow. The second is to keep a member variable of the current index of the table.
Expiring Managed Beans: In the sample project, open up the Faces Config Editor and select the bean: PagingPortletDefaultviewView. You’ll see that the value for the expireWithPageFlow is set to ‘false’. This instructs MWS to keep the managed bean valid until the user’s session expires.
Preserving the current index: Open the Paging Portlet’s Default View and see the currentIndex member variable. This is bound to the Async Table’s First property. That property is the index of the first item to display.
Please see the attached sample project. To use it, after deploying browse to the Public Folders and then the “paging folder”. Page through the list and click on the links in either column to see state passed to the view and/or portlet and then click back. You’ll see the paging state is preserved.
PaginationApp.zip (19.8 KB)