occurs on these tested browsers:- IE7, FF3.5, Safari

The component binding is resolving to null, so the valuechangeListener is no use to setting which page the datapaginator needs to be reset to. The constructor on the data scrolling model sets the row to 0, so get a divide by zero exception. Must figure out why component binding is not working properly (resolving to null) as for compatibility, we will require this. (at all stages through the example of this application, ie: every get for the component binding, it is null).

If placed in session scope with full submit of form, component binding no longer has null value. View scope is creating new instances of bean with partial submit, so must check that out. Also standard jsf example with session scope works with full submit (not partial) for component-binding (doesn't update to new value in partial submit). Must check further.

reason for this problem is ICE-5226 for component-binding

used workaround that if data paginator component binding is null, then look up the component in the tree

I don't think that this issue has be resolved as if I make a backing bean ViewScoped and then perform a partial submit the @PostConstruct method is called again a second time.