ICEfaces
  1. ICEfaces
  2. ICE-6022

ViewState is not correctly applied to all portlets on a page

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0-Beta1
    • Fix Version/s: 2.0.0
    • Component/s: Bridge, Framework
    • Labels:
      None
    • Environment:
      ICEfaces 2 Portlets

      Description

      When there are multiple ICEfaces portlets on a portal page, it appears that the javax.faces.ViewState value is not always correctly applied to all the forms in the portlets.

      For example, using the Chat portlet as an example, assume there are 2 instances on the portal page.

      1) Interact with the first portlet by logging in.

      2) Interact with the second portlet by logging in. At this point, the response contains an update to the first portlet at the <form> level (this should likely be more granular but that's a different issue). The updated form does NOT include the ViewState. There is another update for the ViewState in the response, but it is not correctly applied to the form.

      3) Interact with the first portlet again by sending a message. Since this form does not contain the ViewState, the resulting request results in a new View and the UIViewRoot does not contain the old DOM as an attribute (which it would if the ViewState was provided). The resulting update comes back as a ViewRoot update, replacing the entire page.

      So the issue seems to be center around why the ViewState is not properly restored to the form when it's updated.

        Issue Links

          Activity

            People

            • Assignee:
              Deryk Sinotte
              Reporter:
              Deryk Sinotte
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: