It is also strange that other form fields are cleared.. it again makes me think that something is going wrong between the first and the second call. You may try to backup your current jsp page, rip out all that isn't strictly related to your dataTable and try to track the problem.
Check also that there's an <h:messages> in your page, and look for strange entry in your log. Cosma 2006/5/19, Airstorm <[EMAIL PROTECTED]>:
1) I had originally left the immediate attribute off of my commandSortHeader, but found that other form fields were being cleared when I clicked on a sortable header. Supposedly, having immediate="false" is supposed to fix that, but it still clears the form fields, so I'll just take it off agian for now. 2) The example code I'm looking at is from the latest from Apaches SVN, but you're probably right. I'm sure it should be calling setAscending to make the change (and it makes more sense for the tag library to do that kind of tracking for you). Actually, I should say, I know that it's calling setAscending in my case, but as with setSort, it's always calling setAscending with the boolean value "false", even when clicking on the same column repeatedly. I'll try what you suggested, however, that's the way I originally had it set up, so I don't have much hopes of it fixing it. That's odd that it's calling your setSort equivalent twice and only calling mine once. Even more irksome. :( -- View this message in context: http://www.nabble.com/Sortable+DataTable+in+Tomahawk...-t1643510.html#a4469154 Sent from the MyFaces - Users forum at Nabble.com.
