Quoting Rickard Öberg <[email protected]>:
I'm rewriting the serialization/deserialization to be performed by a separate object rather than being built into the ValueType system. It will be possible to register handlers for specific types (like the JodaTime stuff Niclas added), or it would be possible to replace the entire serializer itself. In such case you could plug in your framework, without having it be part of Qi4j itself.
Sounds great! +1 to that.
Have you looked at the existing Migration library? How would you say that compares to what you are doing?
Currently Migration seems to use JSONObject as state of entity in its methods. Maybe in the future, there would be a separate, independent object to describe a state of Qi4j entity, which would be used in Migration? So that serializator could just give out that state, and it could be used everywhere else in Qi4j? For example, my plug-in could only handle binary <-> Qi4j entity state conversions.
The schemas for entity types of old application versions still need to be kept somewhere in persistent store. Otherwise deserialization of old entities from binary format would be impossible.
_______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
