Uploaded image for project: 'Portlet Bridge'
  1. Portlet Bridge
  2. PBR-244

Request scoped beans and facesmessages are not request scoped after an ActionRequest or ResourceRequest

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 2.1.0.FINAL
    • Fix Version/s: 2.3.0.FINAL
    • Component/s: None
    • Labels:
      None
    • Environment:

      Liferay portal 6.0.6, Jboss PortletBridge 2.1.1-SNAPSHOT, Richfaces 3.3.3

    • Steps to Reproduce:
      Hide

      Create a Richfaces based portlet that has a button on it (Either a4j or h:commandButton). In the actionListener of the commandButton drop a facesMessage. Push the button. After that open the same page on the portal without any parameter. The message will appear again and again until another button is pushed.

      Show
      Create a Richfaces based portlet that has a button on it (Either a4j or h:commandButton). In the actionListener of the commandButton drop a facesMessage. Push the button. After that open the same page on the portal without any parameter. The message will appear again and again until another button is pushed.
    • Estimated Difficulty:
      Medium

      Description

      If there is a user action the request scoped beans and faces messages keep their state until the next user action. It means that if the same page is rendered again in 20 minutes the faces messages will appear and the request scoped beans will remember their property during the next render request. I tried to find this logic of this behavior in the Portlet 2.0 specification but after a quick search I did not succeed.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                kenfinni Ken Finnigan
                Reporter:
                zs_b Balazs Zsoldos
              • Votes:
                2 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 1 day
                  1d
                  Remaining:
                  Remaining Estimate - 1 day
                  1d
                  Logged:
                  Time Spent - Not Specified
                  Not Specified