Hi Pedro, I tried setResponsePage(getPage()) but the problem is it does not re-render controls on the page.
setResponsePage(getPage().getClass()) only works for stateless pages and on most of my pages, I pass params via the constructor. The javascript option will be a last resort, but it seems to be not the most elegant solution. Rgds, On Tue, Nov 10, 2009 at 11:45 AM, Pedro Santos <pedros...@gmail.com> wrote: > if(userSetWasChanged){ > target.appendJavascript("window.location.reload()"); > or > setResponsePage(getPage()); > or > setResponsePage(getPage().getClass()); > } > > > On Tue, Nov 10, 2009 at 5:19 AM, pieter claassen <pieter.claas...@gmail.com> > wrote: >> >> I have a link on a panel that is included in many pages. When the user >> clicks on the link, I change something in the user settings that will >> affect what gets displayed on the page. However, for that to work, I >> need to reload the page after the user clicked on the link as by >> default the other components that now need to be checked for >> conditional visibility don't re-render (why not?). setResponsePage() >> requires me to pass into the panel a target page and this becomes >> complex when you have a mix of statefull and stateless pages as >> targets (and it just doesn't feel right). >> >> I am sure there must be an easier way to just re-render a page? >> >> Any tips? >> >> Thanks, >> pieter >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> > > > > -- > Pedro Henrique Oliveira dos Santos > -- Pieter Claassen musmato.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org