not necessarily. we do not unwrap the exceptions to check for page expired generally, so if you throw it from your code we can catch it and wrap it in a WRE.
-igor On Fri, Jul 10, 2009 at 8:32 PM, James Carman<[email protected]> wrote: > 1.4-rc7 should fix this, no? > > On Fri, Jul 10, 2009 at 10:48 AM, Igor Vaynberg<[email protected]> > wrote: >> you can try unwrapping the exceptions in >> requestcycle.onruntimeexception and call super with the page exipred >> exception. >> >> -igor >> >> On Fri, Jul 10, 2009 at 3:00 AM, Ann Baert<[email protected]> wrote: >>> Hello, >>> >>> How can I throw a PageExpiredException in the constructor of my WebPage? >>> Because the exception is wrapped by Wicket with WicketRuntimeException it >>> goes to the InternalErrorPage. >>> >>> Thanks, >>> Ann >>> **** DISCLAIMER **** >>> <A HREF="http://www.tvh.be/newen/pages/emaildisclaimer.html";> >>> http://www.tvh.be/newen/pages/emaildisclaimer.html </A> >>> >>> "This message is delivered to all addressees subject to the conditions >>> set forth in the attached disclaimer, which is an integral part of this >>> message." >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
