portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ate Douma (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] Reopened: (JS2-780) Provide out-of-the-box Wicket portlet support
Date Wed, 24 Oct 2007 23:01:55 GMT

     [ https://issues.apache.org/jira/browse/JS2-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ate Douma reopened JS2-780:
---------------------------


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.

> 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: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


Mime
View raw message