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? For example, will I run into any problem during deployment/undeployment? What about clustering? Thanks, Yuesong
- Is serialVersionUID really required? Wang, Yuesong
- Re: Is serialVersionUID really required? Johan Compagner
- RE: Is serialVersionUID really required? Wang, Yuesong
- Re: Is serialVersionUID really required? Johan Compagner