Eelco Hillenius wrote: > > 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. > I tried trimming down my app to reproduce it with code that developers could run, but it seems I trimmed too much and the modified now-generic code no longer produces the issue.
> Or do what Al said and throw a RestartResponseException. > This worked fine. -- View this message in context: http://www.nabble.com/setResponsePage-in-a-WebPage-constructor-tf4844887.html#a13913123 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
