On Tue, Sep 9, 2008 at 4:37 PM, Charles Oliver Nutter > I call bug. Deserialization should attempt to use thread context > classloader first. That doesn't fix the JRuby issue, which requires > deeper hooking into the object deserialization, but it would fix yours > (presuming you can set a context classloader).
This is just one of the many reasons why Java serialization is Broken As Designed. Serialization depends on class identity, and class identity in Java depends on the class name and the identity of the classloader. Since classloaders are not serializable, there's no way to be sure you get a valid result when thawing a serialized instance of a class loaded by a non-bootstrap classloader. "Object serialization routinely violates access protection, interferes with class loading, breaks various design patterns, is slow as spit, and in general causes far more problems than it solves." --Elliotte Rusty Harold " > > - Charlie > > > > -- GMail doesn't have rotating .sigs, but you can see mine at http://www.ccil.org/~cowan/signatures --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "JVM Languages" group. To post to this group, send email to jvm-languages@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jvm-languages?hl=en -~----------~----~----~----~------~----~------~--~---
