I disagree. I use Wicket and JDO on GAE/J; it works fine for me, including no serialisation problems.
As a working example, I am satisfied with my Wicket/JDO/GAE/J proof-of- concept web application at www.SwapPlace.co.uk. I am using the lessons learnt for my commercial web site development, which is coming along nicely too. On Oct 3, 9:43 pm, nico <nfmelen...@gmail.com> wrote: > Hey! don't use wicket + GAE!!! you will have lot of serialization problems > and your project will FAIL! you will lose time and money!!!!! > bug:http://code.google.com/p/googleappengine/issues/detail?id=2500 > > Bye! > NM -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
