Both articles avoid the DiskPageStore problem by using the HttpSessionStore, however if you do a search through the mailing list archives for HttpSessionStore you'll find numerous references to problems in using it in the long term and especially in a real, production application, so I don't think that's a good long term solution, so my original question still stands. Is there an alternative or is Wicket perhaps not well suited for use in the App Engine.
Matt ptrthomas wrote: > > Here's another article about Wicket and GAE on DZone: > > http://www.dzone.com/links/rss/wicket_on_google_app_engine.html > > On Sat, Apr 11, 2009 at 8:22 AM, Sergey Podatelev < > brightnesslev...@gmail.com> wrote: > >> Here are a couple of pointers regarding Wicket on GAE: >> >> >> http://www.danwalmsley.com/2009/04/08/apache-wicket-on-google-app-engine-for-java/ >> >> On Sat, Apr 11, 2009 at 6:15 PM, Matthew Welch <matt...@welchkin.net> >> wrote: >> > I've been experimenting a bit with Google App Engine and Wicket and >> things >> > seemed to work fairly well once I turned off the ModificationWatcher. >> > However, I realized that my simple tests were all stateless and that >> once >> > stateful, Wicket would use the DiskPageStore to write some files, which >> is >> > not allowed in the App Engine sandbox. Sure enough, once I added some >> > stateful pages, I started seeing exceptions related to the >> DiskPageStore. >> > >> > I'm a neophyte when it comes to the deep down Wicket internals so I'm >> not >> > sure what my other options might be. In a post Matej Knopp said, ""* >> > DiskPageStore*'s purpose is to store serialized pages on disk in order >> to >> > allow access to previous page versions and also to conserve session >> memory >> > usage." This leads me to believe that using the sassion for storing >> this >> > information isn't a preferred approach. What about the App Engine's >> > datastore (an abstration on BigTable)? That seems like it might be too >> slow >> > to adequately serve this need, but I'm not sure. A thread on >> > Wicket/Terracotta integration ended up with an alternative >> > "SecondLevelCacheSessionStore" but I'm not sure if that is only usable >> with >> > Terracotta or if it might might sense in other situations. Any other >> > options? >> > >> > Also, looking forward, with the knoledge that writing giles and >> spawning >> new >> > threads are not allowed in the App Engine sandbox, are there any other >> items >> > I should be onl the lookout for in Wicket that might make it a poor >> choice >> > for this situation? >> > >> > Matt >> > >> >> >> >> -- >> sp >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > -- View this message in context: http://www.nabble.com/Google-App-Engine-and-Wicket-tp23001592p23007684.html Sent from the Wicket - User 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
