You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Ate Douma (JIRA)" <ji...@apache.org> on 2007/09/17 16:40:56 UTC

[jira] Resolved: (WICKET-658) New Wicket Portlet support: provide a Jetspeed-2 demo installer with wicket-examples configured as portlets out-of-the-box

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

Ate Douma resolved WICKET-658.
------------------------------

    Resolution: Fixed

I've created a new jetspeed-2 demo installer using the latest portlet-support at branch 1.3.0-beta3-portlet-support and the latest jetspeed-2.1.3-dev version which provides Wicket Portlet support out-of-the-box.

t can be downloaded here:

  http://people.apache.org/~ate/wicket/jetspeed-2.1.3-dev-wicket-demo-installer.jar (43Mb)

This new demo showcases both the new WicketExamplesMenuPortlet from which all available Wicket Portlet Examples can be invoked, as well as a separate page showing a few individual Wicket portlets.

Once installed (just choose the default action on every page), you can start the (Tomcat 5.1.23 based) portal by going to the ${installationPath}/bin and run startup.bat or startup.sh.

After 30 seconds or so (please wait until the Tomcat server truly is up and running and logs "INFO: Server startup in xxxx ms"), you can access the portal through:

http://localhost:8080/

The start page contains a short explanation about the Wicket Portlets demo and information how to access the example Wicket portlets from the top menu navigation bar.

I've also uploaded the original wicket-examples.war build from the 1.3.0-beta3-portlet-support branch:

  http://people.apache.org/~ate/wicket/wicket-examples.war (8.4Mb)

That same war is used in the portal demo but you can also deploy it in any standard web server to validate it still runs just as well in a plain servlet container.
There are no portlet-api/container dependencies: portlet-support is only automatically enabled when it discovers a portlet container!

With this last demo I now consider the (initial) portlet-support usable and complete enough for Wicket trunk integration.

> New Wicket Portlet support: provide a Jetspeed-2 demo installer with wicket-examples configured as portlets out-of-the-box 
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-658
>                 URL: https://issues.apache.org/jira/browse/WICKET-658
>             Project: Wicket
>          Issue Type: Sub-task
>          Components: wicket-portlet
>    Affects Versions: 1.3.0-beta2, 1.3.0-beta3
>            Reporter: Ate Douma
>            Assignee: Ate Douma
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.