However... even if it does matter, *in no way* should anyone depend on a serialized session to store data.... if your app can't recover from a clean session, you have bigger problems than not adding a serialVersionId.
- Brill Pappin On 11-Apr-09, at 11:45 PM, Adriano dos Santos Fernandes wrote:
Brill Pappin wrote:If you care about inability to maintain your users sessions after a redeploy, depending on your change, you would not do it. It serves for this purpose as well.Yes, its fine.you really only need to worry about that kind of thing when you are passing java serialized classes between VMs (as in RMI). In fact, you likely don't really even need to bother for Wicket, and you can turn off that check in Eclipse.Adriano --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
smime.p7s
Description: S/MIME cryptographic signature