Serial version UID exists to prevent problems deserializing persistent
serialized data, and since serialization is not being used for long-term
persistent storage in Wicket (unless you have some unusual project going,
sessions should not be persistent across class changes), I cannot see
a need to generate serialversionuids for Wicket components. I personally
just supress the warning.
ZedroS Schwart wrote:
>
> * serialVersionUID and anonymous inner classes
>
> Quite often in my code, I've got some warning due to non define
> serialVersionUID.
>
> I usually tell Eclipse to generate them for me.
>
> However, for the anonymous inner classes, which are quite commun, I'm
> not sure it's ok. Is it ?
>
> Furthermore, I'm wondering which risk I would take by using the
> @SuppressWarnings("serial") annotation. Do you have a clue ?
>
--
View this message in context:
http://www.nabble.com/Wicket%27s-questions-tf3396173.html#a9484189
Sent from the Wicket - User mailing list archive at Nabble.com.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
