Re: Bookmarkable pages and wicket session life-cycle
That means the behavior which i have explained is a normal behavior ? , since in this the links are not resulting in any call backs.. Eelco Hillenius wrote: > >> I have got a question on bookmarkable page and if wicket session's >> life-cycle has any relation with it. >> >> Actually i have a couple of bookmarkable pages in my application (mounted >> through queryurlcodingstrategy). >> >> For scenarios where the session-expiry has reached, invoking any action >> on >> any of the pages results in my custom session-expiry page, which is all >> good, BUT on clicking the links (rendered through ExternalLink and linked >> to >> mounted-url) pointing to the bookmarkable pages, instead of being taken >> to >> the session-expiry page, the bookmarkable pages are rendered, so i wonder >> if >> that is the right behavior? in that case i would have to make those pages >> non-bookmarkable.. > > Well, there is a difference between the bookmarkable pages themselves, > links to those pages (bookmarkablepagelinks) and callbacks on those > pages. Links to bookmarkable pages survive session time outs, but > (stateful) callbacks don't. > > Eelco > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Bookmarkable-pages-and-wicket-session-life-cycle-tp17726662p17728385.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Bookmarkable pages and wicket session life-cycle
> I have got a question on bookmarkable page and if wicket session's > life-cycle has any relation with it. > > Actually i have a couple of bookmarkable pages in my application (mounted > through queryurlcodingstrategy). > > For scenarios where the session-expiry has reached, invoking any action on > any of the pages results in my custom session-expiry page, which is all > good, BUT on clicking the links (rendered through ExternalLink and linked to > mounted-url) pointing to the bookmarkable pages, instead of being taken to > the session-expiry page, the bookmarkable pages are rendered, so i wonder if > that is the right behavior? in that case i would have to make those pages > non-bookmarkable.. Well, there is a difference between the bookmarkable pages themselves, links to those pages (bookmarkablepagelinks) and callbacks on those pages. Links to bookmarkable pages survive session time outs, but (stateful) callbacks don't. Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Bookmarkable pages and wicket session life-cycle
Guys, I have got a question on bookmarkable page and if wicket session's life-cycle has any relation with it. Actually i have a couple of bookmarkable pages in my application (mounted through queryurlcodingstrategy). For scenarios where the session-expiry has reached, invoking any action on any of the pages results in my custom session-expiry page, which is all good, BUT on clicking the links (rendered through ExternalLink and linked to mounted-url) pointing to the bookmarkable pages, instead of being taken to the session-expiry page, the bookmarkable pages are rendered, so i wonder if that is the right behavior? in that case i would have to make those pages non-bookmarkable.. Thank in advance Farhan. -- View this message in context: http://www.nabble.com/Bookmarkable-pages-and-wicket-session-life-cycle-tp17726662p17726662.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
