On 2010-07-31 16.49, Niclas Hedhman wrote:
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...
Ok, then I will go through the API/runtime and remove Serializable so
that this is more clear. To serialize values one would then have to use
toJSON/fromJSON, which explicitly requires the proper Module as context
for deserialization.
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
