It has been bugging me as well. Theoretically, it just might be an issue
- though as currently, with changes in classes the ids are not updated,
this would give problems anyway, but practically, I would be surprised
if anyone came up with a good reason to do this. Except maybe, as Johan
put it (we had this discussion offline), it is good practice to have the
id on all serializable classes.
Eelco
Jonathan Locke wrote:
i was just adding a serialVersionID to the Index page in the
QuickStart project when I realized...
why are we adding these? serialVersionID is generally for persistent
serialized data. since the only reason
half our classes are serializable is to allow clustering, it seems
useless to advise users to do this. it's a pain
and there's no good reason for it... unless there are app containers
that deal with class versioning issues
(maybe they can deal with rolling out new code on only some of the
servers in a cluster...?)... chris, do
you have any thoughts here?
jon
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
