Re: Page Expired when going back to an ajax page
please create a bug report and attach a quickstart that reproduces this. then post the bug number back to this thread. -igor On Feb 1, 2008 10:11 AM, Andrew Williams <[EMAIL PROTECTED]> wrote: > 1.3.0 and 1.3.0-beta4 both exhibit this behaviour. > In fact, 1.3.0 seems worse - it is not just the single most recent > page int he history that still bombs. > > Andy > > > On 1 Feb 2008, at 17:12, Igor Vaynberg wrote: > > > what wicket version are you using? > > > > -igor > > > > > > On Feb 1, 2008 4:06 AM, Andrew Williams <[EMAIL PROTECTED]> wrote: > >> Actually - whilst this fixes the problem when browsing pages far back > >> in the history it does nothing to stop the bug visible if you simply > >> load a page, then another and then hit back - the recently left page > >> seems still to show this issue - a known bug or something new? > >> > >> Andy > >> > >> > >> On 30 Jan 2008, at 22:21, Andrew Williams wrote: > >> > >>> Bad form to reply to myself, but if anyone else had problems with > >>> this there is an undocumented protected method > >>> "onlyTargetActivePage()" which should be called from an overridden > >>> constructor. > >>> > >>> Best wishes, > >>> Andrew > >>> > >>> On 27 Jan 2008, at 15:01, Andrew Williams wrote: > >>> > I have a peculiar problem that I hope can be solved by the experts! > > I have on my application pages a panel that is updated using an > AbstractAjaxTimerBehavior to update the style attribute making it > visible or not. > This works just fine on the current page. If, however, I press the > back button in the browser to show a page that is no longer in the > current session this problem occurs: > > After the time of the ajax timer passes the request is sent for the > panel update and the whole page is replaced by the standard "Page > Expired" exception page. > > Is there a way to change this behaviour so it simply does not > update instead of causing this exception to be thrown? > > Many thanks in advance, > Andrew > > - > 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] > > > > > - > 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]
Re: Page Expired when going back to an ajax page
1.3.0 and 1.3.0-beta4 both exhibit this behaviour. In fact, 1.3.0 seems worse - it is not just the single most recent page int he history that still bombs. Andy On 1 Feb 2008, at 17:12, Igor Vaynberg wrote: what wicket version are you using? -igor On Feb 1, 2008 4:06 AM, Andrew Williams <[EMAIL PROTECTED]> wrote: Actually - whilst this fixes the problem when browsing pages far back in the history it does nothing to stop the bug visible if you simply load a page, then another and then hit back - the recently left page seems still to show this issue - a known bug or something new? Andy On 30 Jan 2008, at 22:21, Andrew Williams wrote: Bad form to reply to myself, but if anyone else had problems with this there is an undocumented protected method "onlyTargetActivePage()" which should be called from an overridden constructor. Best wishes, Andrew On 27 Jan 2008, at 15:01, Andrew Williams wrote: I have a peculiar problem that I hope can be solved by the experts! I have on my application pages a panel that is updated using an AbstractAjaxTimerBehavior to update the style attribute making it visible or not. This works just fine on the current page. If, however, I press the back button in the browser to show a page that is no longer in the current session this problem occurs: After the time of the ajax timer passes the request is sent for the panel update and the whole page is replaced by the standard "Page Expired" exception page. Is there a way to change this behaviour so it simply does not update instead of causing this exception to be thrown? Many thanks in advance, Andrew - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Page Expired when going back to an ajax page
what wicket version are you using? -igor On Feb 1, 2008 4:06 AM, Andrew Williams <[EMAIL PROTECTED]> wrote: > Actually - whilst this fixes the problem when browsing pages far back > in the history it does nothing to stop the bug visible if you simply > load a page, then another and then hit back - the recently left page > seems still to show this issue - a known bug or something new? > > Andy > > > On 30 Jan 2008, at 22:21, Andrew Williams wrote: > > > Bad form to reply to myself, but if anyone else had problems with > > this there is an undocumented protected method > > "onlyTargetActivePage()" which should be called from an overridden > > constructor. > > > > Best wishes, > > Andrew > > > > On 27 Jan 2008, at 15:01, Andrew Williams wrote: > > > >> I have a peculiar problem that I hope can be solved by the experts! > >> > >> I have on my application pages a panel that is updated using an > >> AbstractAjaxTimerBehavior to update the style attribute making it > >> visible or not. > >> This works just fine on the current page. If, however, I press the > >> back button in the browser to show a page that is no longer in the > >> current session this problem occurs: > >> > >> After the time of the ajax timer passes the request is sent for the > >> panel update and the whole page is replaced by the standard "Page > >> Expired" exception page. > >> > >> Is there a way to change this behaviour so it simply does not > >> update instead of causing this exception to be thrown? > >> > >> Many thanks in advance, > >> Andrew > >> > >> - > >> 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]
Re: Page Expired when going back to an ajax page
Actually - whilst this fixes the problem when browsing pages far back in the history it does nothing to stop the bug visible if you simply load a page, then another and then hit back - the recently left page seems still to show this issue - a known bug or something new? Andy On 30 Jan 2008, at 22:21, Andrew Williams wrote: Bad form to reply to myself, but if anyone else had problems with this there is an undocumented protected method "onlyTargetActivePage()" which should be called from an overridden constructor. Best wishes, Andrew On 27 Jan 2008, at 15:01, Andrew Williams wrote: I have a peculiar problem that I hope can be solved by the experts! I have on my application pages a panel that is updated using an AbstractAjaxTimerBehavior to update the style attribute making it visible or not. This works just fine on the current page. If, however, I press the back button in the browser to show a page that is no longer in the current session this problem occurs: After the time of the ajax timer passes the request is sent for the panel update and the whole page is replaced by the standard "Page Expired" exception page. Is there a way to change this behaviour so it simply does not update instead of causing this exception to be thrown? Many thanks in advance, Andrew - 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]
Re: Page Expired when going back to an ajax page
Bad form to reply to myself, but if anyone else had problems with this there is an undocumented protected method "onlyTargetActivePage()" which should be called from an overridden constructor. Best wishes, Andrew On 27 Jan 2008, at 15:01, Andrew Williams wrote: I have a peculiar problem that I hope can be solved by the experts! I have on my application pages a panel that is updated using an AbstractAjaxTimerBehavior to update the style attribute making it visible or not. This works just fine on the current page. If, however, I press the back button in the browser to show a page that is no longer in the current session this problem occurs: After the time of the ajax timer passes the request is sent for the panel update and the whole page is replaced by the standard "Page Expired" exception page. Is there a way to change this behaviour so it simply does not update instead of causing this exception to be thrown? Many thanks in advance, Andrew - 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]
Page Expired when going back to an ajax page
I have a peculiar problem that I hope can be solved by the experts! I have on my application pages a panel that is updated using an AbstractAjaxTimerBehavior to update the style attribute making it visible or not. This works just fine on the current page. If, however, I press the back button in the browser to show a page that is no longer in the current session this problem occurs: After the time of the ajax timer passes the request is sent for the panel update and the whole page is replaced by the standard "Page Expired" exception page. Is there a way to change this behaviour so it simply does not update instead of causing this exception to be thrown? Many thanks in advance, Andrew - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
