[ http://issues.apache.org/jira/browse/TOMAHAWK-103?page=comments#action_12420120 ]
Mike Kienenberger commented on TOMAHAWK-103: -------------------------------------------- Sounds like it might have something to do with the row state values for each row being preserved even though the scroller is actually pointing at different data. If so, there's probably no easy workaround. > inputText doesn't work inside a dataTable with scroll > ----------------------------------------------------- > > Key: TOMAHAWK-103 > URL: http://issues.apache.org/jira/browse/TOMAHAWK-103 > Project: MyFaces Tomahawk > Type: Bug > Components: Data Scroller > Environment: Windows 2000 or XP > Firefox or IE. > Reporter: Tiago Rinck Caveden > > There seems to be a problem using inputText inside dataTables that have a > scroll component. > Independent of how I scrolled on the list, the value of the inputTexts > remained to be the same of the values that should be in the first page only. > (the first values of the query) > Not understanding what was going on, I started trying everything. When I > trade from an inputText to an outputText, then it started working. More > interesting: if I let some columns with outputText, and others with > inputText, then only the formmer would change with the navegation, the latter > would remain always with the first values. > Another detail that might be interesting (or not): I've notice that somthing > might be (wrongly?) cached in memory, because just changing the component > wouldn't make any difference, I had to redo the query (which was kept in the > session) in order for the difference to come. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
