As usual, google provides some interesting opinions on the issue... http://opensource.atlassian.com/projects/hibernate/browse/HBX-964
Issues seem to be with the many ways your objects may be serialized: HTTP Session but more likely various hibernate cache implementations. I would though remind people that the UID is to stop strict validation when serializing between versions of the class. So perhaps not an issue if caches should be flushed between deployments. On Sep 25, 7:31 am, Mike <[EMAIL PROTECTED]> wrote: > When using Hibernate, is it still necessary to include a > serialVersionUID in your java bean classes? I figure since the object > is getting serialized to a database, that the serialVersionUID would > no longer come into play. Can you give me reasons why > serialVersionUID is still needed for Hibernate java beans? Thanks. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
