I'm currently in the process of evaluating frameworks. We are currently using Wicket 1.4.
The ones I've looked at so far have been Vaadin, Tapestry 5.4, and Wicket 6.0. Vaadin I ruled out for various reasons. One of the problems that our users have complained quite a bit about is the dreaded PageExpiration problem. In Wicket 6.0 the issue is resolved somewhat by the framework recreating the page and then issuing a redirect. While understand why it does this // If the page is stateful then we cannot assume that the listener interface is // invoked on its initial state (right after page initialization) and that its // component and/or behavior will be available. That's why the listener interface // should be ignored and the best we can do is to re-paint the newly constructed // page. it's still not the solution we want. The Ajax interaction should continue on as normal. Due to how Tapestry is architected, this is not an isssue. In Wicket 1.4, I got around this somewhat by extending the WebRequestCycleProcessor and recreating the request when a PageExpiration was encountered. It doesn't appear that I can carry this forward in Wicket 6.0. I just want to make sure that I'm not missing anything. Thanks -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-Session-Expiration-Ajax-interactions-tp4655591.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
