datascroller paired page

# Paired <rich:datascroller> components do not work

## Description

Two <rich:datascroller> components bound to the same table aren't synchronized. Having two <rich:datascroller>components on a page, session-scoped beans saves the data for only one <rich:datascroller> component. It is a common pattern to have 2 <rich:datascroller> components: the first in the header, the second in the footer. In this case the first one will not work.

## Links

- Jira

- RichFaces Forum

## How to reproduce

The described above problem occurs if two <rich:datascroller> components are added to any table.

## Causes

The <rich:datascroller> component does not manage the scroll state of a data table.

## Workarounds

The solution is to use "page" attribute and bind it to the same property for all <rich:datascroller> components.