Niclas Hedhman wrote:
During serialization it is not a problem, right? The type of the value is known and can be serialized accordingly.
Right, it's just that we don't serialize type information, only data.
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.
These are two unrelated issues. The value serialization has to do with whether the type information comes from the code declaration or if its embedded in the serialized format. The Association issue is just a visibility issue, since the type information *is* included in the stored format (i.e. the EntityStore is responsible for knowing which EntityType to use when deserializing).
/Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
