On Mon, Apr 6, 2009 at 2:58 PM, Rickard Öberg <[email protected]> wrote:
> Right now I have done a quick-fix by changing getProperty to include > ValueType as a parameter, but it seems weird. One option is to go really > hardcore with state/type separation and have setProperty(name,byte[]) in > EntityState. Then all type handling has to be done in layers above > EntityStore. This makes it tricky to do EntityState serialization though as > the serializer has to have access to both the EntityState and the > EntityType. This is true both for the REST access service and the RDF > indexer, for example. > > I'm not sure how to handle this. Any ideas? I think I suggested previously that there is an EntityTypeService where Stores that needs mapping can retrieve the details of hashed values, such as property types, property names, entity types and so forth. 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
