ICEfaces-EE
  1. ICEfaces-EE
  2. IPCK-388

EE-Accessible-Showcase - Data Paginator exception when using MyFaces

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: EE-3.0.0.GA
    • Fix Version/s: EE-3.2.0.GA
    • Labels:
      None
    • Environment:
      EE-3.0 Build10 (built with Myfaces)
      Server: Tomcat7
      Browsers: all
    • Assignee Priority:
      P2

      Description

      1. In EE-Accessible-Showcase application (built using myFaces JSF), on the Data Paginator page, when clicking to change the page, the following exception is visible in the Tomcat log, and the page is not being changed;
      2. When clicking on the All Components link after going to DataPaginator a similar exception is visible in the server log.

      28-Mar-2012 9:16:18 AM org.icepush.servlet.EnvironmentAdaptingServlet service
      INFO: Falling back to Thread Blocking environment
      java.lang.IllegalStateException: component with duplicate id "j_id_9:j_id_e" fou
      nd
              at org.apache.myfaces.view.facelets.compiler.CheckDuplicateIdFaceletUtil
      s.checkIdsStatefulComponents(CheckDuplicateIdFaceletUtils.java:54)
              at org.apache.myfaces.view.facelets.compiler.CheckDuplicateIdFaceletUtil
      s.checkIdsStatefulComponents(CheckDuplicateIdFaceletUtils.java:75)
              at org.apache.myfaces.view.facelets.compiler.CheckDuplicateIdFaceletUtil
      s.checkIdsStatefulComponents(CheckDuplicateIdFaceletUtils.java:75)
              at org.apache.myfaces.view.facelets.compiler.CheckDuplicateIdFaceletUtil
      s.checkIdsStatefulComponents(CheckDuplicateIdFaceletUtils.java:75)
              at org.apache.myfaces.view.facelets.compiler.CheckDuplicateIdFaceletUtil
      s.checkIdsStatefulComponents(CheckDuplicateIdFaceletUtils.java:75)
              at org.apache.myfaces.view.facelets.compiler.CheckDuplicateIdFaceletUtil
      s.checkIdsStatefulComponents(CheckDuplicateIdFaceletUtils.java:75)
              at org.apache.myfaces.view.facelets.compiler.CheckDuplicateIdFaceletUtil
      s.checkIdsStatefulComponents(CheckDuplicateIdFaceletUtils.java:75)
              at org.apache.myfaces.view.facelets.compiler.CheckDuplicateIdFaceletUtil
      s.checkIdsStatefulComponents(CheckDuplicateIdFaceletUtils.java:35)
              at org.apache.myfaces.view.facelets.DefaultFaceletsStateManagementStrate
      gy.saveView(DefaultFaceletsStateManagementStrategy.java:489)
              at org.apache.myfaces.application.StateManagerImpl.saveView(StateManager
      Impl.java:189)
              at javax.faces.application.StateManager.getViewState(StateManager.java:2
      53)
              at org.icefaces.impl.context.DOMPartialViewContext.renderState(DOMPartia
      lViewContext.java:520)
              at org.icefaces.impl.context.DOMPartialViewContext.processPartial(DOMPar
      tialViewContext.java:222)
              at javax.faces.component.UIViewRoot.encodeChildren(UIViewRoot.java:402)
              at javax.faces.component.UIComponent.encodeAll(UIComponent.java:755)
              at org.apache.myfaces.view.facelets.FaceletViewDeclarationLanguage.rende

        Activity

        Hide
        Mircea Toma added a comment -

        The issue is caused by the use of component binding in the first ice-acc:dataPaginator defined in dataPaginator.xhtml page. It seems this is a known issue that occurs when a component reference is held longer than a JSF lifecycle. More info here: http://myfaces.apache.org/orchestra/myfaces-orchestra-core/component-bindings.html .

        The solution chosen in this case was to remove the binding since the rendered data is not affected.

        Show
        Mircea Toma added a comment - The issue is caused by the use of component binding in the first ice-acc:dataPaginator defined in dataPaginator.xhtml page. It seems this is a known issue that occurs when a component reference is held longer than a JSF lifecycle. More info here: http://myfaces.apache.org/orchestra/myfaces-orchestra-core/component-bindings.html . The solution chosen in this case was to remove the binding since the rendered data is not affected.

          People

          • Assignee:
            Mircea Toma
            Reporter:
            Carmen Cristurean
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: