> On second thought, how does using XML > suddenly magically get rid of the versioning issue?
By itself, it doesn't - but it is more resilient to change because as you evolve a bean, as long as you make sure to provide a default value, things will continue to work. This is because by design, only the changes to a default instance is ever serialized. So if you add a new field, old client code will simply ignore it. If new client code is fed an old bean, it will simply use the default value. It's actually quite clever on Sun's part. /Casper --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
