We're doing exactly that all the time on our wicket/GAE apps and
haven't run into problems. Only thing we had to change was: static
references to components and ajax don't mix well, but one shouldn't do
this anyway.


On 8 May 2010 13:12, Joe Fawzy <joewic...@gmail.com> wrote:
> Hi all
> what are the side effects of setting serialVersionUID  on all page classes
> and components
> private static final long serialVersionUID = 1L;
> i am developing an application which will be deployed on appengine
> appengine handle sessions by storing them in the memcache and data store as
> there is no local filesystem
> for its memcache everything must be Serializable, and as the session is
> stored in the datastore , your session may last for several weeks even if
> the web container expires it
> Ok, when i develop my classes may change a lot hence the
> auto serialVersionUID changes, making appengine complain as its session does
> not expires
> anyway , i think setting private static final long serialVersionUID = 1L; on
> every component will resolve it on appengine side,
> but ,what about wicket side? does it have any implications or side effects?
> thanks
> Joe

To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to