[TRINIDAD-256] Immediate table with required fields are not sortable

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 1.0.1-incubating-core-SNAPSHOT
• Assignee: Unassigned
• Reporter: Simon Lessard
• Created: 06/Jul/06 20:14
• Updated: 09/Aug/07 04:44

Description

Original post about the bug can be found at http://forums.oracle.com/forums/thread.jspa?messageID=1235614&#1235614.

Basically, if an editable <af:table/> contains a required field, sorting and range navigation won't work. This is the correct behavior if the table is not immediate. However, if the table is immediate, then sorting and range navigation should work. The range navigation does work when the table is immeditate, but not the sorting.

My guess is that if a table is immediate, it generate immediate links for the range navigation component but forget to do so on the sorting link in the column header.