Uploaded image for project: 'PUBLIC - Liferay Faces'
  1. PUBLIC - Liferay Faces
  2. FACES-1356

Develop detection of support for POST-REDIRECT-GET design pattern by the portlet container and handle removal of excluded attributes accordingly

    Details

      Description

      Portlet containers like Pluto support the POST-REDIRECT-GET design pattern by first executing the ACTION_PHASE within an HTTP POST request, and then RENDER_PHASE in a subsequent HTTP GET request. Liferay Portal on the other hand does not support this design pattern. Instead, the ACTION_PHASE and RENDER_PHASE are both executed with a single HTTP post request.

      When a portlet container does not support the POST-REDIRECT-GET design pattern, it is necessary to pro-actively remove excluded attributes from the bridge request scope at the beginning of the RENDER_PHASE. The logic for removing excluded attributes is currently in BridgeRequestScopeLiferayImpl.restore(FacesContext) but the method named "restore" does not reflect what's actually going on in the method. Instead, a new method named BridgeRequestScope.removeExcludedAttributes(RenderRequest) method will be created to handle this case.

        Attachments

          Activity

            People

            • Assignee:
              neil.griffin Neil Griffin
              Reporter:
              neil.griffin Neil Griffin
              Participants of an Issue:
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Packages

                Version Package
                liferay-faces-2.1.0-ga1
                liferay-faces-3.0.0-legacy-ga1
                liferay-faces-3.0.0-ga1
                liferay-faces-3.1.0-ga1