On 6/18/11 19:50 , Stanislav Muhametsin wrote:
For a long time, I had idea of asking Core people to make serialization process customizable, so I could plug in my framework into it. I thought of doing it later this year, but it seems now is the time. However, I am not sure if my framework is yet available for public use, and I will ask around about it and let you know.
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.
I'll give you a little idea of how it would work, in my mind currently. There would be a special EntityTypeSchemaService, which would create a Schema (like in Avro) for each entity type needed. To enable versioning, the entity store would need to have its own meta-section, where the schemas for each version would be kept. So, when the entity store of application version X encounters (in the store) entity of version Y and type Z, it would simply look up in the meta-section the schema for entity type Z of version Y to deserialize it.
Have you looked at the existing Migration library? How would you say that compares to what you are doing?
/Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
