Wow. That's an old message. But the answer is that you should use t:saveState on the table's value backing bean (list of row objects)
On 8/22/06, Igor Laberov <[EMAIL PROTECTED]> wrote:
Yes, it is in request scope. I think that the problem is not only in dataTable - all actions in commandLinks aren't invoked in this page. Should I put t:saveState on table or on inputFields? 2006/8/21, Mike Kienenberger <[EMAIL PROTECTED]>: > In that case, it sounds like you have your table data in a request-scoped bean. > You need to use t:saveState to preserve that data to the next request. > Or you can make your backing bean session scoped. > > On 8/21/06, Igor Laberov <[EMAIL PROTECTED]> wrote: > > I had this property. I think that problem is wider, since 'actions' > > from commandLink are not invoked on this page at all. > > > > > > 2006/8/20, Mike Kienenberger <[EMAIL PROTECTED]>: > > > Have you tried marking the dataScroller as immediate="true"? I'm not > > > sure if this gets processed correctly, but that would be the way I'd > > > expect it to work. > > > > > > > > > On 8/20/06, Igor Laberov <[EMAIL PROTECTED]> wrote: > > > > I've created page with inputText and dataTable with scroller. > > > > When inputText has no value and it declares as required="true", the > > > > scroller on the table doesn't work. On the first load the table is > > > > shown OK, but when I try to show next page, no of DataModle methods > > > > are called (no getDataModel, no getDataPage, constructor only). As a > > > > result, the table stays on the same first page. > > > > > > > > The problem is disappeared if inputText is declared as > > > > required="false", but this of course is workaround only. > > > > If I put selectOneMenu combo list, the situation is worse - > > > > required="false" doesn't help here! > > > > > > > > I must admit that no error was printed in console. > > > > Thank you, > > > > Igor > > > > > > > > > >
