[JS2-780] Provide out-of-the-box Wicket portlet support

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.1.3, 2.2.0
• Fix Version/s: 2.1.3, 2.2.0
• Component/s: Assembly/Configuration, Bridges
• Assignee: Ate Douma
• Reporter: Ate Douma
• Created: 12/Sep/07 12:14
• Updated: 04/Oct/11 21:07
• Resolved: 24/Oct/07 23:04

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.