ICEfaces
  1. ICEfaces
  2. ICE-8610

ice:outputFormat displays incorrect information when above table

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: EE-1.8.2.GA_P04
    • Fix Version/s: EE-1.8.2.GA_P05
    • Component/s: ICE-Components
    • Labels:
      None
    • Environment:
      Chrome, FF, IE9, Tomcat 7.0.17, JBoss 7.1
    • Assignee Priority:
      P2

      Description


      If ice:dataTable is tied to a backing bean value that may be reduced via a type ahead filter and place a paginator element at the bottom of the table with a text like "Page X/X. Display rows 5-10 of 50" it will always display the correct information. But, if you put the same ice:outputFormat at the top of the table, then select a page past page one, then type something in the filter in order to reduce the number of rows per page, the text will get mangled like "Page 1/1. Display rows -19 from 31-11".

      To reproduce:
      1. Deploy sample source code.
      2. Go to http://localhost:8080/ICEfacesEE-1.8.2-P04/case11634.iface
      3. Switch to the last page
      4. Click on 'Filter' button

        Activity

        Migration created issue -
        Repository Revision Date User Message
        ICEsoft Public SVN Repository #31249 Mon Oct 01 17:33:49 MDT 2012 art.zambrano ICE-8610 fixed issue with returning incorrect displayedRowsCount and firstRowIndex values by ensuring that the first row is within range
        Files Changed
        Commit graph MODIFY /icefaces/trunk/icefaces/component/src/com/icesoft/faces/component/datapaginator/DataPaginatorRenderer.java
        Hide
        Arturo Zambrano added a comment - - edited

        Committed fix to the trunk at revision 31249.
        The problem is that the associated data table is returning and incorrect value for getFirst(), i.e. the index of the first row being displayed. This is because, in JSF 1.2 this value is not automatically updated when the data object is modified dynamically. Fortunately, the ICE extension of HtmlDataTable has a method to ensure that the first row is within range. It is just necessary to call it when the paginator begins its rendering phase. This fix is not applicable to a plain h:dataTable, since it doesn't have a similar method.

        Show
        Arturo Zambrano added a comment - - edited Committed fix to the trunk at revision 31249. The problem is that the associated data table is returning and incorrect value for getFirst(), i.e. the index of the first row being displayed. This is because, in JSF 1.2 this value is not automatically updated when the data object is modified dynamically. Fortunately, the ICE extension of HtmlDataTable has a method to ensure that the first row is within range. It is just necessary to call it when the paginator begins its rendering phase. This fix is not applicable to a plain h:dataTable, since it doesn't have a similar method.
        Migration made changes -
        Field Original Value New Value
        Reporter Migration [ remote ] Evgheni Sadovoi [ evgheni.sadovoi ]
        Migration made changes -
        Attachment ICEfacesEE-1.8.2-P04.rar [ 14886 ]
        Migration made changes -
        Assignee Ken Fyten [ ken.fyten ]
        Migration made changes -
        Assignee Ken Fyten [ ken.fyten ] Arturo Zambrano [ artzambrano ]
        Fix Version/s EE-1.8.2.GA_P05 [ 10331 ]
        Assignee Priority P2 [ 10011 ]
        Migration made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Ken Fyten made changes -
        Status Resolved [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            Arturo Zambrano
            Reporter:
            Evgheni Sadovoi
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: