Hi,
In theory, all Serializable classes should have a serialVersionUID, but
to provide one to every annonymous inner class used everywhere in a
Wicket app is just too much. So I decided to turn off that warning in
Eclipse, and not to use serialVersionUID any more, but what is the
implication?
not that importand
it is just easier to cluster over different jvms (which doesnt happen a lot)
but it is also easier to upgrade an existing code. Because the generated
serialVersionUID
does change for the most stupid ways (i guess they have to do that but most
of the time i don;t care if i added
Compagner [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 14, 2008 11:06 AM
To: users@wicket.apache.org
Subject: Re: Is serialVersionUID really required?
not that importand
it is just easier to cluster over different jvms (which doesnt happen a
lot) but it is also easier to upgrade an existing
, February 14, 2008 11:06 AM
To: users@wicket.apache.org
Subject: Re: Is serialVersionUID really required?
not that importand
it is just easier to cluster over different jvms (which doesnt happen a
lot) but it is also easier to upgrade an existing code. Because the
generated serialVersionUID
