serialVersionID should be used if we want to support this:

1> If 2 compilers are used and 2 running machines talk to each other. (not very likely and they just must use the same source compiler)
2> X servers running slightly different versions of wicket (update one but not the other)
3> Session deserialization so that after a restart (and an update of wicket) all the session can be read into memory.


1 and 2 i don't mind. They all should just use the same exact version over all the servers.
Those only really apply to jre core classes (some machines running 1.4.2_05 and others 1.5)


but 3 is the question do we want to support this?

johan


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

Reply via email to