Thiago Leão Moreira:
I'm playing around with Wicket 1.4.8 and Liferay trunk and the portlets are working fine.
Hello Thiago! (and HI to others too!)
It seems you have some experience regarding Wicket + Liferay, so, maybe you will be able to help me a bit, I hope
I'm currently in R&D of Wicket-based portlets for Liferay. More or less everything seems to be OK, except the fact that I can't find a way to register more than 1 portlet per Wicket application.
Wicket portlets in Liferay [somehow] have limitation, that portlet name should be the same as Wicket filter path. In this case everything seems to work as expected, notably AJAX support. But if I change portlet name (or filter path) - I'm getting in trouble with broken AJAX support (at best). To be more precise, I'm getting following error on any AJAX request (monitored via Firefox javascript console): The requested resource (/forms-portlet/wicketFilter/) is not available, where "forms-portlet" is context of my Wicket portlet web application and "/wicketFilter" is path on which Wicket filter is configured in web.xml (as opposed to "/wicketPortlet" in working configuration below).
This is my configuration which works:
portlet.xml
<portlet-app xmlns="http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="2.0" xsi:schemalocation="http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd
http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd">
<portlet>
<description>Wicket Portlet</description>
<portlet-name>[b]wicketPortlet[/b]</portlet-name>
<display-name>wicketPortlet</display-name>
<portlet-class>org.apache.wicket.protocol.http.portlet.WicketPortlet</portlet-class>
<init-param>
<name>wicketFilterPath</name>
<value>/[b]wicketPortlet[/b]</value>
</init-param>
<supports>
<mime-type>text/html</mime-type>
<portlet-mode>VIEW</portlet-mode>
<portlet-mode>EDIT</portlet-mode>
</supports>
<supports>
<mime-type>text/xml</mime-type>
<portlet-mode>VIEW</portlet-mode>
<portlet-mode>EDIT</portlet-mode>
</supports>
<supported-locale>en</supported-locale>
<resource-bundle>Language</resource-bundle>
</portlet>
</portlet-app>
and web.xml
...
<filter>
<filter-name>wicketApplication</filter-name>
<filter-class>org.apache.wicket.protocol.http.WicketFilter</filter-class>
<init-param>
<param-name>applicationFactoryClassName</param-name>
<param-value>org.apache.wicket.spring.SpringWebApplicationFactory</param-value>
</init-param>
<init-param>
<param-name>applicationBean</param-name>
<param-value>wicketApplication</param-value>
</init-param>
</filter>
<filter-mapping>
<filter-name>wicketApplication</filter-name>
<url-pattern>/[b]wicketPortlet[/b]/*</url-pattern>
<dispatcher>REQUEST</dispatcher>
<dispatcher>INCLUDE</dispatcher>
<dispatcher>FORWARD</dispatcher>
</filter-mapping>
[i]<!-- These are added by Liferay upon deployment -->
<servlet>
<servlet-name>wicketPortlet</servlet-name>
<servlet-class>com.liferay.portal.kernel.servlet.PortletServlet</servlet-class>
<init-param>
<param-name>portlet-class</param-name>
<param-value>org.apache.wicket.protocol.http.portlet.WicketPortlet</param-value>
</init-param>
<load-on-startup>0</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>wicketPortlet</servlet-name>
<url-pattern>/wicketPortlet/*</url-pattern>
</servlet-mapping> [/i]
...
Please note, that portlet name and Wicket filter path are the same. As I told before, the problem with such configuration is that I cannot register more that one portlet per Wicket filter (and Wicket filter = Wicket application), and that's exactly what I'm trying to achieve (2+ portlets running in the same Wicket application context).
Please, if you (or anybody else reading this) have something to suggest or somehow guide me in correct direction - I will be very grateful for your help!
Thanks in advance!
P.S. I'm currently using 1.4.10 version of Wicket framework.