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/06/14 19:21:25 UTC

[jira] Created: (WICKET-657) New Wicket Portlet support: adapting wicket-examples to use the new portlet support so they can be run as portlets

New Wicket Portlet support: adapting wicket-examples to use the new portlet support so they can be run as portlets  
--------------------------------------------------------------------------------------------------------------------

                 Key: WICKET-657
                 URL: https://issues.apache.org/jira/browse/WICKET-657
             Project: Wicket
          Issue Type: Sub-task
          Components: wicket-portlet
    Affects Versions: 1.3.0-beta2
            Reporter: Ate Douma




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

[jira] Resolved: (WICKET-657) New Wicket Portlet support: adapting wicket-examples to use the new portlet support so they can be run as portlets

Posted by "Ate Douma (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ate Douma resolved WICKET-657.
------------------------------

    Resolution: Fixed

I've adapted the wicket-examples to support running as portlets by:
- upgrading web.xml to the servlet api 2.4
- replacing WicketFilter by WicketPortletFilter in web.xml
- configuring Jetspeed-2 specific implementations for the required org.apache.portals.bridges.common.ServletContextProvider and org.apache.portals.bridges.common.PortletResourceURLFactory interfaces in web.xml
- added a dependency on the portlet-api-1.0 (note: this one is to be "provided" by portals)
- adding a portlet.xml providing WicketPortlet instances mapped to WicketPortletFilter paths in web.xml

That's it.

The wicket-examples can still be accessed directly as plain web application, but also (at the same time) as portlets :)

Note: not all examples do work, although the majority does.
For some of the examples this is understandable like with the FramesApplication which I think never can be run in a portal.
And the same goes for the link to the source code provided in every example.

But the Ajax Debug Window works quite nicely, as most of the Ajax examples.
I'd anyone interested to try it out themselves, I definitely need feedback and review on all of this.

To help out with testing, I'm going to provide a custom jetspeed-2.1.1-wicket-installer.jar with all wicket portlets already installed and accessible through the Jetspeed-2 page menus.
That's going to be the next subtask/issue.

> New Wicket Portlet support: adapting wicket-examples to use the new portlet support so they can be run as portlets  
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-657
>                 URL: https://issues.apache.org/jira/browse/WICKET-657
>             Project: Wicket
>          Issue Type: Sub-task
>          Components: wicket-portlet
>    Affects Versions: 1.3.0-beta2
>            Reporter: Ate Douma
>


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