Details

      Description

      {markdown}
      Steps to reproduce:

      1. Deploy the jsf-showcase-portlet and navigate to it.
      2. Navigate to the [h:commandButton Navigation example](http://localhost:8080/web/guest/showcase/-/jsf-tag/h/commandbutton/navigation).
      3. Click the Ajax checkbox.
      4. Click the To Param Page > button.

      If the bug still exists, you will be redirected to the following URL:

      http://localhost:8080/web/guest/showcase?p_auth=ModzcrYt&p_p_id=1_WAR_jsfshowcaseportlet400SNAPSHOT&p_p_lifecycle=1&p_p_state=normal&p_p_mode=view&p_p_col_id=column-1&p_p_col_count=1&_1_WAR_jsfshowcaseportlet400SNAPSHOT_componentPrefix=h&_1_WAR_jsfshowcaseportlet400SNAPSHOT_foo=1234&_1_WAR_jsfshowcaseportlet400SNAPSHOT_componentUseCase=navigation&_1_WAR_jsfshowcaseportlet400SNAPSHOT_componentName=commandbutton&_1_WAR_jsfshowcaseportlet400SNAPSHOT__facesViewIdRender=%2Fviews%2Fcomponent.xhtml

      And the page will display "Successfully executed *non-JSF postback*..."

      The reason for this issue is that `BridgeRedirectURLLiferayImpl` is not a wrapper for `BridgeURLImpl`, so the special `_bridgeAjaxRedirect` parameter is applied to `BridgeRedirectURLLiferayImpl` but not to the wrapped `BridgeRedirectURLImpl` which is used to obtain the actual URL.{markdown}

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Packages

                Version Package
                bridge-impl-2.0.0
                bridge-impl-3.0.0
                bridge-ext-1.0.0
                bridge-ext-2.0.0
                bridge-ext-3.0.0
                bridge-ext-5.0.0
                bridge-api-2.0.0
                bridge-api-3.0.0
                bridge-api-4.0.0
                bridge-impl-4.0.0
                bridge-impl-5.0.0