On Wed, Jan 26, 2011 at 3:23 PM, Matthias Keller <[email protected]> wrote: > My current solution which solves this problem (although ugly) is the > following code in the onClick:
You could try to see if "setRedirect(true);" works for you, and not perform a setResponsePage( new Page()), but rather do a setResponsePage(Page.class). However, that would make the confirmation page bookmarkable, something you probably don't want :) Ugly use case sometimes requires ugly code :-).. I don't think this is ugly, it performs each step you need explicitly. The use case to remove pages from the page map is not that common, so the story for doing that is not as nice. Perhaps something like a "@DontStoreInPageMap" annotation could be used. This would put the page in the session, ensuring you still have the stateful programming model and are able to work with the page as if it were a normal wicket page. But the page would not be put in the pagestore. I guess this would still work across clusters to support failover: the current page would still be stored in the session, making it available on all buddy nodes. Martijn --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
