|
It should be a dataTable issue. To workaround this, you must 'rewind'
it manually with dataTable.setFirst(0); if some data was changed. You
can do this in bean, that performs searching . 2 Adrian Mitev: Have you any informations on this dataTable issue? I've faced out, that it's totally unflexible to fix the problem such way. I'm thinking about storing of 'last' record count in session or component state directly in Scroller. The dataTable then cann be 'refreshed' automaticly, if record count has changed since last rendering :) regards, paul Beelen, Marco schrieb:
|
- Re: Issue with the t:dataScroller Paul Iov
- Re: Issue with the t:dataScroller Mike Kienenberger
- Re: Issue with the t:dataScroller Paul Iov
- Re: Issue with the t:dataScroller Mike Kienenberger
- RE: Issue with the t:dataScroller Beelen, Marco
- Re: Issue with the t:dataScroller Mike Kienenberger
- Re: Issue with the t:dataScrol... Paul Iov
- Re: Issue with the t:dataS... Mike Kienenberger
- Re: Issue with the t:dataS... Paul Iov
- Re: Issue with the t:dataS... Mike Kienenberger
- Re: Issue with the t:dataS... Paul Iov

