If you're working with a web app, you'll want your objects to be serializable if you put them on the session. In a clustered environment that involves replicating sessions between app servers, the built-in serialization mechanism is used to pass those objects over the wire. An app server could potentially serialize objects and write them to disk to conserve memory. Some app servers may use serialization to preserve objects on the session through a restart as well.
On Sep 24, 5:31 pm, 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 -~----------~----~----~----~------~----~------~--~---
