swapplace isn't a good example, it is too simple
When you said
don't use wicket + GAE!!! you will have lot of serialization
problems
did you mean to say
don't use wicket + GAE for complex applications!!! you will have
lot of serialization
swapplace isn't a good example, it is too simple
NM
On Mon, Oct 4, 2010 at 5:19 AM, Ian Marshall ianmarshall...@gmail.comwrote:
Mmmm: my link has been Googlised. If interested, try
http://www.SwapPlace.co.uk
instead.
On Oct 4, 9:11 am, Ian Marshall ianmarshall...@gmail.com wrote:
I
Wicket works fine on GAE as long as you make sure your page instances
do not contain non-Serializable instances - using detachable models
follows this rule.
Here is this base class I use to set up a Wicket / Engine App
public abstract class EngineApplication extends WebApplication
{
Mmmm: my link has been Googlised. If interested, try
http://www.SwapPlace.co.uk
instead.
On Oct 4, 9:11 am, Ian Marshall ianmarshall...@gmail.com wrote:
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
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,
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
On Wed, Sep 29, 2010 at 12:24 PM, Eurig Jones eurigjo...@gmail.com wrote:
You're probably using the same Wicket setup as I am - Sessions are
stored in the datastore.
The Jetty local development set-up clearly doesn't emulate the real
thing exactly by the looks of it. But by using LoadableDetachableModel
the list is populated once per request and detached when the
I had the same issue with Wicket / JPA combination.
My particular problem was that I was using a ListView by passing a
List directly into the constructor:
ListViewPost listView = new ListViewPost(id, myListObject)
{ ... }
My solution was to instead use a LoadableDetachableModel for the
This looks like a fine approach as detachable models will make it
cheaper to Serialize I guess. Were you able to find the reason why it
gave error before and works now?
I am curious to know what happens when you create a new collection of
myListObject and not use LoadableDetachableModel.
On Sep
