Re: Problems with Page Expiration
Martin Grigorov-4 wrote If the login page is really stateless then it will never throw PageExpiredException. It seems some component/behavior in the login page is stateful. Use org.apache.wicket.devutils.stateless.StatelessChecker (wicket-devutils) or debug org.apache.wicket.Page#isPageStateless() to find why the page is stateful Thanks for the response. I suspected as much but when I put a breakpoint in isPageStateless(), it always returns true for each call made when I refresh the login page. Again, with setRecreateMountedPagesAfterExpiry set to false, pressing the login button always takes me to the timout page set by setPageExpiredErrorPage. I don't get it. Initially I thought it was something in our templating mechanism. Our platform allows an advanced user to design the login screen. I skipped that and reduced my test to just a StatelessForm on a page. Same result. The page is a subclass and makes use of wicket:extend but the parent class doesn't do anything but set the page title. I've checked my authorization strategy and I don't see anything problematic. No doubt it will be something silly but at the moment I'm perplexed. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Problems-with-Page-Expiration-tp4664774p4664807.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Problems with Page Expiration
Try to reproduce it in a quickstart and attach it to Jira. Martin Grigorov Wicket Training and Consulting On Wed, Mar 5, 2014 at 7:14 PM, Brad Grier brad.gr...@salusnovus.comwrote: Martin Grigorov-4 wrote If the login page is really stateless then it will never throw PageExpiredException. It seems some component/behavior in the login page is stateful. Use org.apache.wicket.devutils.stateless.StatelessChecker (wicket-devutils) or debug org.apache.wicket.Page#isPageStateless() to find why the page is stateful Thanks for the response. I suspected as much but when I put a breakpoint in isPageStateless(), it always returns true for each call made when I refresh the login page. Again, with setRecreateMountedPagesAfterExpiry set to false, pressing the login button always takes me to the timout page set by setPageExpiredErrorPage. I don't get it. Initially I thought it was something in our templating mechanism. Our platform allows an advanced user to design the login screen. I skipped that and reduced my test to just a StatelessForm on a page. Same result. The page is a subclass and makes use of wicket:extend but the parent class doesn't do anything but set the page title. I've checked my authorization strategy and I don't see anything problematic. No doubt it will be something silly but at the moment I'm perplexed. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Problems-with-Page-Expiration-tp4664774p4664807.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Problems with Page Expiration
Martin Grigorov-4 wrote Try to reproduce it in a quickstart and attach it to Jira. Martin Grigorov Wicket Training and Consulting I created a quickstart using the Wicket Examples statelessform page as the home page. If setRecreateMountedPagesAfterExpiry is false, the page expires on form submit. I'll submit the quickstart but I still find it hard to believe it's a bug. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Problems-with-Page-Expiration-tp4664774p4664820.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Problems with Page Expiration
When setRecreateMountedPagesAfterExpiry is true in our app, redirecting to a custom timeout page either through setPageExpiredErrorPage or via catching a PageExpiredException isn't working (the exception never makes it to onException in IRequestCycleListener). When set to false, the redirect works fine but my stateless login page immediately throws a PageExpiredException when the login form is submitted. If I make the form stateful, everything works but of course my login page eventually expires. This is something we want to avoid. We're using Wicket 6.14. Any thoughts? -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Problems-with-Page-Expiration-tp4664774.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Problems with Page Expiration
Hi, On Tue, Mar 4, 2014 at 11:32 PM, Brad Grier brad.gr...@salusnovus.comwrote: When setRecreateMountedPagesAfterExpiry is true in our app, redirecting to a custom timeout page either through setPageExpiredErrorPage or via catching a PageExpiredException isn't working (the exception never makes it to onException in IRequestCycleListener). When set to false, the redirect works fine but my stateless login page immediately throws a PageExpiredException when the login form is submitted. If the login page is really stateless then it will never throw PageExpiredException. It seems some component/behavior in the login page is stateful. Use org.apache.wicket.devutils.stateless.StatelessChecker (wicket-devutils) or debug org.apache.wicket.Page#isPageStateless() to find why the page is stateful If I make the form stateful, everything works but of course my login page eventually expires. This is something we want to avoid. We're using Wicket 6.14. Any thoughts? -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Problems-with-Page-Expiration-tp4664774.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
