|
In fact, you can avoid this if you use a subform surrounding your
required inputs (or group of inputs). Regards, Sebastian. [EMAIL PROTECTED] wrote: Hi, this little question is related to : http://issues.apache.org/jira/browse/ADFFACES-45After testing the current behavior, the bug isn't totally accurate. If a table has its "immediate" attribute set to true, and does have a field input "required" at true (such as an inputText) it is totally possible to have Range or Sort nagivation on the table. (like by clicking on the header of the table when a column is "sortable"). However, there is still a bug happening that is : The "required" field never get sorted like others columns do. The column's values stay idle while others columns really get resorted. This leads to an out of sync problem. SO, my suggestion would be to totally block sorting events on a table when there is at least 1 column that has the attribute "required" at true AND that the table has the attribute "immediate" at true too. Any comments regarding this, thanks Pierre-Luc Archambault Fujitsu Consulting --
Sebastian Fiorentini |
- Sorting when an "immediate" table contain... Pierre-Luc_Archambault
- Re: Sorting when an "immediate" tabl... Sebastián Fiorentini
- Re: Sorting when an "immediate" ... Pierre-Luc_Archambault
