Martin Marinschek wrote:
Sorry,
don't know so many details about the data-scroller, but I think Thomas
said that this is a problem still to be overcome.
Maybe you would want to work on that and provide a patch?
I solved the problem by making my own scroller controller class
which has a request scope, the scroller controller delivers
the page count var name via: pageIndexVar="#{scrollerController.scroller}"
this one is called whenever the page counter is initialized or set
at that stage I pull the value out of the local scope
push it into a session scope and
then I can access it from outside and push it back into the request
cyle at a different time, sort of hackish but seems to work, since
the scroller checks if the pageCount already is set in the request cycle
or not.
