Comments on: Apache Wicket on Google App Engine for Java

By: Looking at MVC frameworks « cg2p

Looking at MVC frameworks « cg2p — Wed, 30 Mar 2011 14:07:54 +0000

[...] going to distract myself with this just yet though. I know it can work in App Engine from previous. I’m going to get some basic application up and running first [...]

By: Improve Performance By Using Keys Only Query on Google App Engine « Making a better world with enterprise Java

Sat, 05 Mar 2011 09:50:19 +0000

[...] It has been around two months since we started to port an existing application on Google App engine. It used Hibernate for persistence, Wicket framework for web layer and Spring as an Ioc container. Looking at the will it play on appengine we had to change Hibernate to use either JPA or JDO. We decided on JPA purely on the basis of experience we had on JPA compared to JDO. Wicket is semi compatible and we made it work by the three standard workarounds described here. [...]

By: Managing Wicket Serialization Problem On Google App Engine « Making a better world with enterprise Java

Thu, 24 Feb 2011 04:53:19 +0000

[...] App engine will it play suggests that if you have a wicket project you follow this workaround your Wicket project will start working on app engine. Still, one of the error you may [...]

By: Managing Wicket Serialization Problem On Google App Engine « Inphina Thoughts

Wed, 20 Oct 2010 15:25:22 +0000

[...] App engine will it play suggests that if you have a wicket project you follow this workaround your Wicket project will start working on app engine. Still, one of the error you may [...]

By: Improve Performance By Using Keys Only Query on Google App Engine « Inphina Thoughts

Sat, 11 Sep 2010 13:25:40 +0000

By: Generating Excel Files On Google App Engine For A Wicket Application « Inphina Thoughts

Wed, 08 Sep 2010 21:16:15 +0000

[...] We are porting an existing Wicket application on Google App Engine. This application uses Wicket, Spring and Hibernate. If you read will it play in app engine, you will notice that Wicket is semi compatible and it does work with workarounds. Hibernate on the other hand is incompatible and Spring is fully supported. We began porting this application after changing persistence to use JPA finstead of hibernate. We used workarounds for wicket described here. [...]

By: Problems When Deploying Working Application on Google App Engine « Inphina Thoughts

Sun, 05 Sep 2010 13:21:40 +0000

[...] use jpa for persistence in Google App engine here. Wicket does work with the workarounds mentioned here. For wicket application we need to enable sessions in app engine config [...]

By: bob

bob — Wed, 03 Feb 2010 02:25:45 +0000

i had to add serialVersionUID to my wicket pages since they are stored in the session and serialized. I guess they are not required by Eclipse when I create a wicket page. before i did that, i was receiving an exception like:

javax.servlet.ServletException: java.lang.RuntimeException: java.io.InvalidClassException: wicket.LoginPage; local class incompatible: stream classdesc serialVersionUID

By: Tee Bee

Tee Bee — Wed, 15 Jul 2009 01:51:32 +0000

I agree that it works fine in Eclipse using the Google appengine plugin, but after deplyoying to Google the first page was ok, but trying to simulate some other pages I get this error: 500 Server error
and the logs is:

Uncaught exception from servlet
com.google.apphosting.api.ApiProxy$RequestTooLargeException: The request to API call datastore_v3.Put() was too large.

any idea?

regards

By: Per

Per — Sat, 27 Jun 2009 21:39:17 +0000

Really been trying this but can’t get it working in the app engine. It works fine in Eclipse but on Google I get a 404 – so I wonder where the difference is.