Uploaded image for project: 'Wicket'
  1. Wicket
  2. WICKET-647

New Wicket Portlet support



    • Type: New Feature
    • 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:
    • Environment:
      Jetspeed-2.1.2, Tomcat 5.5, Servlet API 2.4, JDK 1.4 & Java 5


      I'm providing a new solution for Wicket Portlet support, see also my initial proposal on the wicket-dev list: http://www.nabble.com/A-new-proposal-for-Wicket-Portlet-support-tf3836652.html

      As this solution will require a few (but not very much) changes to Wicket core, I'll create a separate branch first to let everyone involved review and test it out.
      I'll also create separate sub tasks in JIRA to record the changes required and the new features provided so each can be reviewed individually and we can have step-by-step discussions how to proceed in bringing this solution into the main trunk.

      Note: as current Wicket development is getting close to the 1.3.0 release, I don't expect all of this to be merged into the trunk until after the 1.3.0 release.
      But some of my proposed changes really are very light and non-intrusive, so I can imagine (and hope) those can be integrated in the trunk even before the 1.3.0 release.
      That definitely would make it easier for me to provide portlet support to my own development team using the wicket core trunk and only a few additional patches.


        New Wicket Portlet support: create a separate branch for review Sub-task Resolved Ate Douma
        New Wicket Portlet support: fix appending query parameters Sub-task Resolved Ate Douma
        New Wicket Portlet support: use a RequestContext for abstracted url generation, writing header response and namespacing Sub-task Resolved Ate Douma
        New Wicket Portlet support: extending IHeaderResponse and its usage to allow plugging in custom HeaderResponse writing Sub-task Resolved Ate Douma
        New Wicket Portlet support: translating Wicket relative paths back to fully qualified paths for usage in a portlet context Sub-task Resolved Ate Douma
        New Wicket Portlet support: Encode Wicket urls through RenderContext to allow a PortletRenderContext to replace them by PortletURLs Sub-task Resolved Ate Douma
        New Wicket Portlet support: adding portlet support with a new WicketPortlet and support classes Sub-task Resolved Ate Douma
        New Wicket Portlet support: adapting wicket-examples to use the new portlet support so they can be run as portlets Sub-task Closed Ate Douma
        New Wicket Portlet support: provide a Jetspeed-2 demo installer with wicket-examples configured as portlets out-of-the-box Sub-task Resolved Ate Douma
        New Wicket Portlet support: Merge WicketPortletFilter back in WicketFilter using a delagate class for handling and (class) loading the portlet specific functionality Sub-task Resolved Ate Douma
        New Wicket Portlet support: Support non-relative urls in Ajax.Request redirect callback handling Sub-task Resolved Ate Douma
        New Wicket Portlet support: Support for detached/popup pages Sub-task Resolved Ate Douma



            • Assignee:
              ate Ate Douma
              ate Ate Douma
            • Votes:
              0 Vote for this issue
              0 Start watching this issue


              • Created: