[
http://opensource.atlassian.com/projects/hibernate/browse/HBX-964?page=co...
]
Dan Allen commented on HBX-964:
-------------------------------
Your comments are very insightful. I am very keen on having this documented, regardless
of which road is choosen because it is one of those debates that eats up many hours of the
day as developers argue back and forth over it. You are right, Eclipse triggered a debate
that rarely occurred before it added its "warning" flag, and as it appears, for
little reason.
I do feel that the Serializable interface is important. Therefore, I am not going to try
to convince you otherwise because what you have said makes complete sense. I would like to
see you add an abbreviated version of this reasoning into the documentation.
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