On Sat, Jul 31, 2010 at 6:09 AM, Rickard Öberg <[email protected]> wrote: > > On 2010-07-30 16.49, Marc Grue wrote: >> >> I have a problem serializing a ValueComposite when I pass it from one page >> to another in Wicket. Wicket is checking if the properties of the >> Shouldn't Wicket be able to serialize my >> UserEntityDTO, or am I missing something basic? >> >> I think Niclas was working around this issue in >> http://old.nabble.com/ValueComposites-are-not-%27type-proxied%27-like-other-Composites.-td22072609.html#a22072609 > > Hm... I think the Composite extends Serializable is a left-over. They > shouldn't be. Am I missing something Niclas? The problem is that the > deserialization process needs a lot of context (i.e. you need your own > ObjectInputStream that has access to Composite factories and whatnot), and I > don't think we ever figured out how to do that properly.
No, I think you are right. Waaaaaayyyyyy back in time, I think in 2007 in the second generation of the code (we are now 4th generation if I remember correctly), everything was serializable and what not. The issue mentioned in the above thread is http://issues.ops4j.org/browse/QI-181, which is about our own entity serialization mechanism that wasn't clever enough to figure out which ValueComposite type to instantiate... Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
