Jetspeed 2
  1. Jetspeed 2
  2. JS2-780

Provide out-of-the-box Wicket portlet support

    Details

      Description

      Wicket portlet-support is coming along quite nicely now (see: WICKET-647).
      With the latest changes (see: WICKET-656#action_12525400) WicketPortlet required factory classnames init parameters can now also be provided through a WicketPortlet.properties file defined in the org.apache.wicket.protocol.http.portlet package.
      These factory classnames are the only portal specific configurations needed to use Wicket as portlet development framework.
      By providing our own WicketPortlet.properties defining our jetspeed specific factory classnames, we can provide Wicket portlet support out-of-the-box, no other configurations needed!

      I'll add this properties configuration to our jetspeed-commons project so its available for all applications.

        Activity

        Hide
        Ate Douma added a comment -

        For Wicket 1.3.0-beta5, portlet-support will be disabled by default as under certain circumstances a Wicket application is not to be used for portlet rendering, even when deployed in a portlet supporting web container/server, see WICKET-1100.

        To provide still out-of-the-box portlet support for Wicket applications, a global (default) property can be provided in the WicketPortlet.properties.
        As Jetspeed already provides this properties file (through jetspeed-commons), I'll add this new configuration property, org.apache.wicket.detectPortletSupport=true.

        Show
        Ate Douma added a comment - For Wicket 1.3.0-beta5, portlet-support will be disabled by default as under certain circumstances a Wicket application is not to be used for portlet rendering, even when deployed in a portlet supporting web container/server, see WICKET-1100 . To provide still out-of-the-box portlet support for Wicket applications, a global (default) property can be provided in the WicketPortlet.properties. As Jetspeed already provides this properties file (through jetspeed-commons), I'll add this new configuration property, org.apache.wicket.detectPortletSupport=true.

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development