Gabriel, did you consider offering the patch to the wicketstuff project? Maybe those changes are general improvements for all of us. Thanks for sharing anyway!
On Tue, Nov 25, 2014 at 7:49 PM, Gabriel Landon <[email protected]> wrote: > I know it's not the error you report, but did you add > "liferay-web-xml-enabled=false" in the liferay-plugin-package.properties > file. > I had to do that to have portlet work with liferay 6.1 and 6.2 > see : > > http://apache-wicket.1842946.n4.nabble.com/wicket-portlet-and-liferay-6-1-td4650001.html > > Also I'm not using PageParameters, but constructors : > setResponsePage(new MyClass(param1, param2, ...)) > > I also had to tweak a few files in the wicketstuff-portlet : > -PortletRequesMapper (to handle > BookmarkableListenerInterfaceRequestHandler) > -WicketPorlet and ResponseStat (to fix some ajax issues) > wicketstuff-portlet-6.jar > < > http://apache-wicket.1842946.n4.nabble.com/file/n4668558/wicketstuff-portlet-6.jar > > > > But still from time to time I've got problem with wicket-portlet and > liferay > with an infinite loop that use 100% CPU. Unfortunatly I'm not skilled > enough > in Porlet spec to fix this. So from my point of view wicketstuff-portlet is > not production safe anymore... > > Hope this help, > Gabriel. > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Wicket6-setResponsePage-stackoverflow-error-tp4668538p4668558.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
