So my project has used Wicket (albeit perhaps not well) on it's last couple projects. We are now adopting ExtJS. If I use a page transition style (reloading the browser page in it's entirely each time), I can populate the onReady() in each load, and I only have on Wicket stateful page on the backend to cooperate with.
But some folks have expressed interest in using an Ext tab control to maintain multiple pages at once and service each independently. So I could load page A, do some work on it, maybe get interrupted by a coworker asking for something else, open page B, do some work, and never lose my uncommitted work in A as I worked with B and submitted it. The problem here (and i admit that I am a neophyte in both Ext and Wicket, knowing just enough in each to get by) is that as I understand it, Wicket stores the state of the current page on the server. So as soon as I loaded B, A became invalid and submitting A, or issuing AJAX calls from A would look like a new page arrival to it. Am I wrong? Is there a way around this? How can I make Ext and Wicket friends because I really am fond of major portions of each and if I can make the marriage work, I think it has the potential to be a rocking way to develop apps. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-ExtJS-tp3882229p3882229.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
