We are running Wicket + Liferay (Webspace) in Glassfish 2, and experience no problems; IIRC Glassfish uses the same Catalina engine as Tomcat?
> > For AJAX/resource requests, another supports element for mime-type > "text/xml" is needed. This sounds like a Tomcat issue, our portlets use Ajax fine without such a mime-type setting. > 2) Name congruence in deployment descriptors > > The name in the pattern under //filter-mapping/url-pattern in web.xml > (e.g. "/testPortlet/*") has to match with the value under > //portlet/portlet-name in portlet.xml, otherwise the portlet will not > be > rendered, or you get StackOverflowExceptions in LR. Again, possibly a Tomcat issue, in Glassfish we use e.g. a name "LocalMessagesPortlet" with the filter-mapping /localmessages/* with no issues > "The requested resource (/hellowicket-portlet-1.0- > SNAPSHOT/testPortlet/) > is not available." instead of the actual portlet content. I would recommend using a more readable build/finalName pom.xml setting instead of the version-appended artifact name unless you want to deploy multiple versions. - Tor Iver --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
