On Tue, Mar 3, 2009 at 7:43 AM, Francisco Diaz Trepat - gmail <[email protected]> wrote: > Hi all, I decided to ask for help, since last night I had nightmares of xml > files extrangulating me. > I read the portlet how-to in the wiki, probably misread it. I have an > application that has no portlet usage (as in no blabla extends blaportlet), > but I was told that all the application could be seen from inside a portle, > simply by configure xmls: > > web.xml > portlet.xml > sun-web.xml > > (using Netbeans, wicket 1.4rc2, glassfish v3, portlet-container from > open-portal project) > > > I have this on the web.xml: > > <filter> > <filter-name>WicketFilter</filter-name> > > <filter-class>org.apache.wicket.protocol.http.WicketFilter</filter-class> > > <!-- portlet support --> > <init-param> > <param-name>portletOnlyFilter</param-name> > <param-value>true</param-value> > </init-param> > > <init-param> > <param-name>detectPortletContext</param-name> > <param-value>true</param-value> > </init-param> > > > <init-param> > <param-name>configuration</param-name> > <param-value>development</param-value> > </init-param> > > <init-param> > <param-name>filterMappingUrlPattern</param-name> > > <param-value>/MyApplicationThatDoesNotWorkWithPortlet/*</param-value> > </init-param> > > I have this on the portlet.xml: > > <portlet-app id="MyApplicationThatDoesNotWorkWithPortlet"> > <portlet> > <description> MyApplicationThatDoesNotWorkWithPortlet > portlet version</description> > <portlet-name> MyApplicationThatDoesNotWorkWithPortlet </portlet-name> > <display-name> MyApplicationThatDoesNotWorkWithPortlet - > Portlet</display-name> > > <portlet-class>org.apache.wicket.protocol.http.portlet.WicketPortlet</portlet-class> > > <init-param> > <name>wicketFilterPath</name> > <value>/MyApplicationThatDoesNotWorkWithPortlet</value> > </init-param> > > <expiration-cache>-1</expiration-cache> > <supports> > <mime-type>*/*</mime-type> > <portlet-mode>VIEW</portlet-mode> > </supports> > <portlet-info> > <title>MyApplicationThatDoesNotWorkWithPortlet</title> > > <keywords>Portlet MyApplicationThatDoesNotWorkWithPortlet</keywords> > </portlet-info> > </portlet> > </portlet-app> > > finally I have this on the sun-web.xml: > > <sun-web-app error-url=""> > <context-root>/MyApplicationThatDoesNotWorkWithPortlet</context-root> > <class-loader delegate="true"/> > <jsp-config> > <property name="keepgenerated" value="true"> > <description>Keep a copy of the generated servlet class' java > code.</description> > </property> > </jsp-config> > </sun-web-app> > > Please, could someone help me out. I couldn't find a comprehensive guide to > these 3 xml file and I am sure that I am missing something.
I suggest looking at the web.xml and portlet.xml in wicket-examples [1]. That's what I did and I had my Wicket app running as a portlet in no time. One thing I miss in your filter configuration is the init-param 'applicationClassName' which should have your Wicket application class as value. HTH, Niels [1] http://svn.apache.org/repos/asf/wicket/releases/wicket-1.4-rc2/wicket-examples/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
