[
http://opensource.atlassian.com/projects/hibernate/browse/HBX-964?page=co...
]
jahlborn commented on HBX-964:
------------------------------
@max: the very same argument could be made for the "magic" value computed by the
jvm. it is just a hash of a bunch of different stuff, and there is no guarantee that
incompatible changes to the class will not result in the same serialVersionUID.
that said, why not just add an optional property to the hbm file so users can specify them
directly (like <meta attribute="serialversionUID">), this is probably the
correct solution as it allows users to decide when incompatible changes have been made.
that would put us in the very same spot we are already in when writing our own java files.
when we change the hbm file incompatibly, we should change the serialVersionUID.
add serialVersionUID to entity classes
--------------------------------------
Key: HBX-964
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HBX-964
Project: Hibernate Tools
Issue Type: Improvement
Components: hbm2java
Affects Versions: 3.2beta10
Reporter: Dan Allen
Priority: Minor
Attachments: HBX-964-v1.txt
Original Estimate: 5 minutes
Remaining Estimate: 5 minutes
The serialVersionUID is recommended for classes that implement java.io.Serializable. The
hbm2java task should either set the serialVersionUID to 1L or automatically generate a
value. I prefer setting it to 1L because it is easy and it will work, but if you feel
motivated, you can look at what Eclipse does to generate this value from the class
signature.
I have included a patch that just sets it to 1L.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira