Actually I don't see any reason why to redirect for stateless pages, but browsing the source code I found that the default WePageRenderer returns true for org.apache.wicket.request.handler.render.PageRenderer.enableRedirectForStatelessPage(). Should I override this method as well to disable the redirect? But therfore I have to provide my own WebPageRenderer in WebApplication.class. By the way, we have a bunch of AbstractAjaxBehaviors and AjaxLinks in the component hierarchy which trigger the Page to be "stateful". But I don't have experience with stateless components so I may miss something.
-- View this message in context: http://apache-wicket.1842946.n4.nabble.com/REDIRECT-TO-BUFFER-render-strategy-and-Wicket-6-8-0-tp4658991p4659041.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
