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

New Wicket Portlet support: use a RequestContext for abstracted url generation, writing header response and namespacing

    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

      To support rendering in a Portlet container, wicket needs to abstract the (final) url, markupId generation and writing the IHeaderResponse.

      I'm going to provide a new base RequestContext class which default implementation (for standard web application purposes) really doesn't do anything.

        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: