On Wed, Aug 26, 2009 at 10:31 AM, Rickard Öberg<[email protected]> wrote: > The problem is that the > Property in your Entity then points to a type that Qi4j cannot really know > what it is, and therefore it is set to be of SerializableType (since type is > designated based on type rather than actual instance). Then you will see > exactly the result you get. > > The only way to get around that is to somehow include > type information in the serialized state whenever the actual instance does > not conform to the type of the property that declared it.
During serialization it is not a problem, right? The type of the value is known and can be serialized accordingly. During deserialization, we have a similar problem to the Association discussed in separate thread, that the referenced type is not visible from the module where it is being deserialized. If the limitation instead is that the value composite must be visible from the module, then I have a hard time understanding the problem. And if we go that route, I think the same limitation should exist for the Associations. 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
