Let's assume we have a state holder bean, in session or view scope. Now let's add a standard request scope bean, to hold our component binding, and act as a a controller. In the faces-config.xml, add the following:

<managed-bean>
<managed-bean-name>stateHolder</managed-bean-name>
<managed-bean-class>org.icefaces.StateHolder</managed-bean-class>
<managed-bean-scope>session</managed-bean-scope>
</managed-bean>

<managed-bean>
<managed-bean-name>controller</managed-bean-name>
<managed-bean-class>org.icefaces.Controller</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
<managed-property>
<property-name>stateHolder</property-name>
<value>#

</value>
</managed-property>
</managed-bean>

Now, the controller can use component bindings as well as regular ValueBindings to the display, and receive events. It doesn't matter that it can't hold state, since it has a reference to the session scoped bean, which simply holds long-term state.

Added a request scoped bean to hold the component binding, and to receive the ValueChangeEvent which made use of the component binding. Didn't need to tie the two beans together, since the new controller only needed static state from the model.

Subversion 21550
glimmer\compat\samples\component-showcase\src\org\icefaces\application\showcase\view\bean\examples\component\dataPaginator\DataScrollingController.java
glimmer\compat\samples\component-showcase\src\org\icefaces\application\showcase\view\bean\examples\component\dataPaginator\DataScrollingModel.java
glimmer\compat\samples\component-showcase\web\WEB-INF\includes\examples\custom\dataTable-dataScrolling.xhtml

This was the only component binding in compat component-showcase.

it doesn't work, the state holder bean is also reload when dataPaginator or another component with partiall submit is clicked

the state holder bean has view scope