ICEfaces
  1. ICEfaces
  2. ICE-1021

Fix dataTable, dataPaginator, single selection rowSelector

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 1.5
          • Fix Version/s: 1.8.2
          • Component/s: ICE-Components
          • Labels:
            None
          • Environment:
            Operating System: All
            Platform: All

            Description

            If you use a dataTable with a dataPaginator, so that the table rows are split
            over more than one page, and add a rowSelector with multipleSelection="false",
            then it is possible to actually do multiple selection, as long as you're
            selecting rows on different pages.

              Issue Links

              is duplicated by

              Bug - A problem which impairs or prevents the functions of the product. ICE-2513 rowSelector: multiple=false still allows multiple selection

              • Major - Major loss of function.
              • Closed

                Activity

                Ascending order - Click to sort in descending order
                Hide
                Permalink
                Alok Mittal added a comment -

                There is workaround for this issue on the backing bean side. Assuming the usual code (table backed by a list, and the field 'selected' to indicate selection):

                <pre>

                public void onRowSelect( RowSelectorEvent e )
                {
                // Clear all selections first
                selectedObject = null;
                for ( ListIterator<Type> i = myList.listIterator(); i.hasNext()

                { i.next().setSelected( false ); }

                // Get the selected row from the event, and explicitly select it
                Type rowObject = myList.get( e.getRow() );
                if ( e.isSelected() )

                { rowObject.setSelected( true ); selectedObject = rowObject; }

                }

                </pre>

                Show
                Alok Mittal added a comment - There is workaround for this issue on the backing bean side. Assuming the usual code (table backed by a list, and the field 'selected' to indicate selection): <pre> public void onRowSelect( RowSelectorEvent e ) { // Clear all selections first selectedObject = null; for ( ListIterator<Type> i = myList.listIterator(); i.hasNext() { i.next().setSelected( false ); } // Get the selected row from the event, and explicitly select it Type rowObject = myList.get( e.getRow() ); if ( e.isSelected() ) { rowObject.setSelected( true ); selectedObject = rowObject; } } </pre>
                Hide
                Permalink
                Ken Fyten added a comment -

                Assigned for retest.

                Show
                Ken Fyten added a comment - Assigned for retest.
                Hide
                Permalink
                Joanne Bai added a comment - - edited
                • Glimmer revision: 21299
                  The data table in Row Selection of current compat showcase is single page, in which data paginator does not apply.
                • 1.8.2-EE-p01 revision 21302
                  Row selector works properly with dataPaginator
                  Tested with Tomcat6.0.26 + FF3.6 and IE8
                Show
                Joanne Bai added a comment - - edited Glimmer revision: 21299 The data table in Row Selection of current compat showcase is single page, in which data paginator does not apply. 1.8.2-EE-p01 revision 21302 Row selector works properly with dataPaginator Tested with Tomcat6.0.26 + FF3.6 and IE8

                  People

                  • Assignee:
                    Unassigned
                    Reporter:
                    Mark Collette
                  • Votes:
                    1 Vote for this issue
                    Watchers:
                    0 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: