[
https://issues.apache.org/jira/browse/JS2-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ate Douma resolved JS2-780.
---------------------------
Resolution: Fixed
> Provide out-of-the-box Wicket portlet support
> ---------------------------------------------
>
> Key: JS2-780
> URL: https://issues.apache.org/jira/browse/JS2-780
> Project: Jetspeed 2
> Issue Type: Improvement
> Components: Assembly/Configuration, Bridges
> Affects Versions: 2.1.3, 2.2
> Reporter: Ate Douma
> Assignee: Ate Douma
> Priority: Minor
> Fix For: 2.1.3, 2.2
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
