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

New Wicket Portlet support: Merge WicketPortletFilter back in WicketFilter using a delagate class for handling and (class) loading the portlet specific functionality

    Details

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

      Description

      I moved the usage of all portlet api specific classes in WicketPortletFilter to a separately class, WicketFilterPortletContext, which will only be created when running in a portlet container.
      As effect, the resulting WicketPortletFilter code doesn't depend on the portlet api anymore, so using it within a non-portlet container context (plain Tomcat or Jetty for instance) is now possible too.

      But, now the remaing code in WicketPortletFilter really does do much itself anymore and can easily be integrated back in WicketFilter without problems.

      I've decided to do so as it makes Wicket portlet support even less intrusive as it was before: no need to configure a different filter anymore in web.xml !

        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: