Uploaded image for project: 'Wicket'
  1. Wicket
  2. WICKET-647 New Wicket Portlet support
  3. WICKET-654

New Wicket Portlet support: translating Wicket relative paths back to fully qualified paths for usage in a portlet context

    Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.3.0-beta2, 1.3.0-beta3
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      Wicket has the very nice feature of only generating current page relative url paths which is great when working behind mod_proxy.

      But for a portlet, their is no such thing as "current request path", and thus relative paths makes no sense here.
      Actually, the WicketPortlet solution will rewrite all wicket urls as PortletURL with the targetted wicket url as embedded parameter.

      So, when running in a portlet context (RenderContext.isEmbedded()), the Request.getRelativePathPrefixToContextRoot() and .getRelativePathPrefixToWicketHandler() need to adapted to return a prefix which will make the generated wicket url fully qualified again against the base/domain url.
      This might seem like a problem for environments behind mod_proxy (and it might), but when you run a portal this is a common/known issue.

      The changes I'll commit against this issue are only effective when RenderContext.isEmbedded() == true, so this will have no effect in the normal case.

        Attachments

          Activity

            People

            • Assignee:
              adouma Ate Douma
              Reporter:
              adouma Ate Douma
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: