[
https://issues.apache.org/jira/browse/HTTPCORE-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472093
]
Roland Weber commented on HTTPCORE-41:
--------------------------------------
Hi Oleg,
after having another look into the serialization spec, I'd like to remove the
serialVersionUID from our classes altogether. If we want to support migration
of serialized data in the presence of "evolution", we should have a concept and
test cases. If we don't, we shouldn't set serialVersionUID so that the
serialization mechanism can detect changes. Or did I interpret something wrong
in the spec?
The generated values are not random but can be computed using the serialver
tool, so there is no need to change them.
cheers,
Roland
(I've see version-based serialVersionUIDs at work.)
> define non-random serialVersionUID
> ----------------------------------
>
> Key: HTTPCORE-41
> URL: https://issues.apache.org/jira/browse/HTTPCORE-41
> Project: HttpComponents Core
> Issue Type: Improvement
> Affects Versions: 4.0-alpha3
> Reporter: Roland Weber
> Assigned To: Roland Weber
> Priority: Trivial
>
> Serializable classes have a serialVersionUID which seems to be an
> auto-generated hash that does not give any indication on how to update it.
> Replace with a definition based on the component version, for example:
> serialVersionUID = 0x400a4L
> for version 4.0, fixlevel 0, alpha 4.
> Let me know what you think,
> Roland
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
