Details

    • Similar Issues:
      Show 5 results 

      Description

      The outputLink seems to be broken in JSF 2.1 after I upgraded my liferay from 5.2.3 to 6.0 and JSF from 1.2 to 2.1

      <h:outputLink style="color: #0000FF;text-decoration:underline;" value="#

      {lookupBean.portalContext}

      /group/customercenter/fund-request">
      </h:outputLink>

      In JSF 1.2, the outputLink rendered was /namingportal/group/customercenter/fund-request

      In JSF 2.1, the outputLink rendered is /vcc_portlets/namingportal/group/customercenter/fund-request. It also appending the webapp context to the outputLink. Did the behavior of outputLink changed part of JSF 2.1?

      Thanks

        Issue Links

          Activity

          Hide
          Srividhya added a comment -

          Neil

          I think I found another way to get the #

          {liferay.portalURL}. I am getting it from the HttpServletRequest. Once I replaced the #{liferay.portalURL}

          with my

          {baseURL}

          from HttpServletRequest my code worked fine.

          Here is my code
          StringBuffer requestURL = request.getRequestURL();
          String baseURL = StringUtils.substringBefore(requestURL.toString(), ("/" + <CONTEXT_NAME>));

          Thanks
          Sri

          Show
          Srividhya added a comment - Neil I think I found another way to get the # {liferay.portalURL}. I am getting it from the HttpServletRequest. Once I replaced the #{liferay.portalURL} with my {baseURL} from HttpServletRequest my code worked fine. Here is my code StringBuffer requestURL = request.getRequestURL(); String baseURL = StringUtils.substringBefore(requestURL.toString(), ("/" + <CONTEXT_NAME>)); Thanks Sri
          Hide
          Neil Griffin added a comment -

          Sounds good Srividhya. Glad you found a workaround.

          Show
          Neil Griffin added a comment - Sounds good Srividhya. Glad you found a workaround.
          Hide
          Neil Griffin added a comment -

          Update: I think that guess about serialization/deserialization was right and that you will be able to use #

          {liferay.portalURL}

          when FACES-1168 is fixed. Please "watch" that issue for updates, since this issue is closed.

          Show
          Neil Griffin added a comment - Update: I think that guess about serialization/deserialization was right and that you will be able to use # {liferay.portalURL} when FACES-1168 is fixed. Please "watch" that issue for updates, since this issue is closed.
          Hide
          Neil Griffin added a comment - - edited

          I'm re-opening this issue because it turns out that Srividhya is exactly right, particularly in regard to the way URLs are being rendered by the bridge.

          I recently found out that Wesley Hales of JBoss filed the following "TCK Challenge" issue:
          https://issues.apache.org/jira/browse/PORTLETBRIDGE-217

          In response, Michael Freedman fixed the MyFaces Portlet Bridge Reference Implementation (RI) so that it has the same behavior as JBoss Portlet Bridge:
          https://issues.apache.org/jira/browse/PORTLETBRIDGE-215

          When I upgraded to the latest version of the TCK (FACES-1364), I found that it was necessary to fix Liferay Faces Bridge in a similar manner. Both ExternalContext.encodeActionURL(String) and ExternalContext.encodeResourceURL(String) are affected.

          Show
          Neil Griffin added a comment - - edited I'm re-opening this issue because it turns out that Srividhya is exactly right, particularly in regard to the way URLs are being rendered by the bridge. I recently found out that Wesley Hales of JBoss filed the following "TCK Challenge" issue: https://issues.apache.org/jira/browse/PORTLETBRIDGE-217 In response, Michael Freedman fixed the MyFaces Portlet Bridge Reference Implementation (RI) so that it has the same behavior as JBoss Portlet Bridge: https://issues.apache.org/jira/browse/PORTLETBRIDGE-215 When I upgraded to the latest version of the TCK ( FACES-1364 ), I found that it was necessary to fix Liferay Faces Bridge in a similar manner. Both ExternalContext.encodeActionURL(String) and ExternalContext.encodeResourceURL(String) are affected.
          Hide
          Neil Griffin added a comment -

          Note that you may need to add the following URL query parameter before it will be encoded correctly:
          ?javax.portlet.faces.DirectLink=true

          Show
          Neil Griffin added a comment - Note that you may need to add the following URL query parameter before it will be encoded correctly: ?javax.portlet.faces.DirectLink=true

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Development

                  Structure Helper Panel