> But I'm getting inconsistent results for different web pages. When the > validity check fails it always appears to call the "setResponsePage()" but > sometimes will display the DifferentPage in the browser (i.e. what I want) > but sometimes continues to display the OriginalPage (not what I want). > > Am I not supposed to be doing a setResponsePage() in a webpage's > constructor? Is setResponsePage() only for form/ajax submission? How can I > accomplish what I'm after here?
You should always be able to use setResponsePage with Wicket 1.3 (in 1.2, this is not entirely supported). If you found a bug, please see if you can create a reproducible test case for it. Or do what Al said and throw a RestartResponseException. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
