Away for long time, but now back with great news. (Hey Jeremy! Eelco! Martijn!)
Like I've tweeted a few minutes ago, I've implemented a BigTableGAEPageStore for Wicket so we can advance another step further full compatibility with Google App Engine. The project can be seen at http://code.google.com/p/gawcket It is a fork of wicket-gae-template with a modified Guestbook to not use LoadableDetachableModel and the BigTableGAEPageStore. With this said, you can go to http://gawcket.appspot.com and test it. Submit the form a few times and then modify the URL to reference an older version. You can check this video on YouTube to see how data is being stored at GAE's Datastore: http://youtu.be/ObvA9ao8U2Q I just hope I've done everything correctly on this implementation. So I ask the experts to take a look, and more important: to try it on your apps that run on more than one CPU at GAE. Thank you, Long live Wicket!! Bruno Borges www.brunoborges.com.br +55 21 76727099 "The glory of great men should always be measured by the means they have used to acquire it." - Francois de La Rochefoucauld On Tue, Sep 21, 2010 at 3:01 PM, Rodolfo Hansen <[email protected]> wrote: > There is also an archetype I wrote that works with the maven-gae-plugin > > mvn archetype:generate -DarchetypeGroupId=net.kindleit > -DarchetypeArtifactId=gae-archetype-wicket -DarchetypeVersion=0.7.1 \ > > -DgroupId=com.myapp.test -DartifactId=testapp > > > > On Tue, 2010-09-21 at 13:40 +0200, Ernesto Reinaldo Barreiro wrote: > > > There is already a GAE template project somewhere on goggle code [1]. > > Would it make sense to try to contact the author and join forces with > > other GAE users? > > > > Cheers, > > > > Ernesto > > > > 1-http://code.google.com/p/wicket-gae-template/ > > > > > > On Tue, Sep 21, 2010 at 1:19 PM, nino martinez wael > > <[email protected]> wrote: > > > It would make perfect sense for me if there appeared a wicketstuff > > > project(subclasses necessary for compability with GAE) for this along > > > with an example project.. > > > > > > 2010/9/20 Jeremy Thomerson <[email protected]>: > > >> On Mon, Sep 20, 2010 at 1:18 PM, tetsuo <[email protected]> > wrote: > > >> > > >>> An auto-detected GAE-specific mode in Wicket core? I don't think this > is a > > >>> good idea... > > >>> > > >> > > >> I agree that this shouldn't go in core, but I think if someone like > Clint > > >> has the motivation to do so, I'd love to see a project that provides > > >> out-of-the-box GAE support. This might make it easier for newbs to > get > > >> something deployed to play with. This could potentially be done as a > > >> standalone project that provides subclasses to WebApplication, etc, > with the > > >> default implementations switched out to GAE-compatible classes, > configured > > >> correctly, etc. Or, it could be a git clone of 1.4 and 1.5 (trunk) > that > > >> keeps current with the "vendor" (us, official Wicket), but adds in > their > > >> custom changes to make it GAE compatible. > > >> > > >> Why not use Jira sub tasks? > > >> > > >> > > >> I think this is the way to go - create a master "make GAE compatible > > >> version" task and subtasks for each individual thing. There should be > a > > >> differentiation made between ones that can be accepted in core and > those > > >> that can't. For example, we (probably) won't be accepting a > WebApplication > > >> subclass specific to GAE. But, we could accept some changes that need > to be > > >> made to make it compatible with, or easier to make compatible with, > GAE. > > >> For example, I'd love to see a task for "kill the use of stupid > TreeModel > > >> in 1.5" (and, really, any java.awt / javax.swing usage in core). But, > this > > >> would be better discussed as a separate thread. > > >> > > >> -- > > >> Jeremy Thomerson > > >> http://www.wickettraining.com > > >> > > > > > >
