ICEfaces
  1. ICEfaces
  2. ICE-10395

ace:dataTable - pagination is reset on row selection inside composite comp.

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Invalid
    • Affects Version/s: EE-3.3.0.GA_P02, 4.0
    • Fix Version/s: EE-4.0.0.GA, EE-3.3.0.GA_P03
    • Component/s: ACE-Components
    • Labels:
      None
    • Environment:
      JSF 2.1.18 and up, Composite Component
    • Assignee Priority:
      P1
    • Support Case References:
    • Workaround Exists:
      Yes
    • Workaround Description:
      Use Mojarra 2.1.6 if possible or use the dataTable outside of the composite component interface.

      Description

      In this scenario the ace:dataTable is used in a composite component. The table renders a paginator as well as uses row selection. If the table is moved to a new page and the row is selected, the table gets set back to the first page.

      This seems to be an issue since the Mojarra 2.1.6. Using this release with the EE 3.3.0 P02 release doesn't show this issue. It also is an issue with the 4.0.0 and Mojarra 2.2.7 release.

      Even though the execute and render attributes are set to @this, the entire table gets rendered and updated.

        Activity

        Hide
        Arran Mccullough added a comment -

        Attached test case that shows the issue.

        Steps:

        • Load welcomeICEfaces.jsf
        • Move the paginator to the second page.
        • Select a row, paginator moves it back to the first page.
        Show
        Arran Mccullough added a comment - Attached test case that shows the issue. Steps: Load welcomeICEfaces.jsf Move the paginator to the second page. Select a row, paginator moves it back to the first page.
        Hide
        Mircea Toma added a comment - - edited

        The so called issue is caused by testcomp:dataTable's 'page' attribute that is not bound to any bean. The testcomp:dataTable component defines the default value of the 'page' to the be the empty string, value that gets converted to 0. This causes the page index to be reset to 0 on every request.

        Show
        Mircea Toma added a comment - - edited The so called issue is caused by testcomp:dataTable 's 'page' attribute that is not bound to any bean. The testcomp:dataTable component defines the default value of the 'page' to the be the empty string, value that gets converted to 0. This causes the page index to be reset to 0 on every request.

          People

          • Assignee:
            Mircea Toma
            Reporter:
            Arran Mccullough
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: