You are viewing a plain text version of this content. The canonical link for it is here.
Posted to adffaces-issues@incubator.apache.org by "Simon Lessard (JIRA)" <ad...@incubator.apache.org> on 2006/07/06 13:14:30 UTC
[jira] Created: (ADFFACES-45) Immediate table with required fields
are not sortable
Immediate table with required fields are not sortable
-----------------------------------------------------
Key: ADFFACES-45
URL: http://issues.apache.org/jira/browse/ADFFACES-45
Project: MyFaces ADF-Faces
Type: Bug
Reporter: Simon Lessard
Priority: Minor
Original post about the bug can be found at http://forums.oracle.com/forums/thread.jspa?messageID=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.
--
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
[jira] Updated: (ADFFACES-45) Immediate table with required fields
are not sortable
Posted by "Pierre-Luc Archambault (JIRA)" <ad...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/ADFFACES-45?page=all ]
Pierre-Luc Archambault updated ADFFACES-45:
-------------------------------------------
After 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" (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.
> Immediate table with required fields are not sortable
> -----------------------------------------------------
>
> Key: ADFFACES-45
> URL: http://issues.apache.org/jira/browse/ADFFACES-45
> Project: MyFaces ADF-Faces
> Issue Type: Bug
> Reporter: Simon Lessard
> Priority: Minor
>
> Original post about the bug can be found at http://forums.oracle.com/forums/thread.jspa?messageID=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.
--
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
[jira] Updated: (ADFFACES-45) Immediate table with required fields
are not sortable
Posted by "Matthias Weßendorf (JIRA)" <ad...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/ADFFACES-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthias Weßendorf updated ADFFACES-45:
---------------------------------------
Affects Version/s: 1.0.1-incubating-core-SNAPSHOT
> Immediate table with required fields are not sortable
> -----------------------------------------------------
>
> Key: ADFFACES-45
> URL: https://issues.apache.org/jira/browse/ADFFACES-45
> Project: MyFaces ADF-Faces
> Issue Type: Bug
> Affects Versions: 1.0.1-incubating-core-SNAPSHOT
> Reporter: Simon Lessard
> Priority: Minor
>
> Original post about the bug can be found at http://forums.oracle.com/forums/thread.jspa?messageID=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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.