Łukasz, Just a heads-up,
Thanks for reporting these two issues. I am on it straight away, and hopefully can find out quickly what is happening in each. I'll be back with answers a bit later. Cheers 2009/10/2 Łukasz Zieliński <[email protected]>: > Hello, > It looks like ValueComposite properties are not always serialized. I define > an entity with value property of type Foo, now this value in turn has two > properties: > interface Foo { > Property<String> bar(); > BazProperty baz(); > } > interface BazProperty extends Property<String> {} > When entity is created and after UnitOfWork.apply() is called serialize for > looks like this (edited to focus on properties): > "properties":{ > "identity":"9c70bea0-3ea8-4d56-98c0-e508c2cdc2ab-0", > "foo":{"bar":"Bar"} > }, > Baz got lost somewhere along the way :). I first encountered this when using > Jdbm ES however snippet above was extracted from MemoryEntityStoreService > instance. > Now I'm leaning towards position that using such properties in > ValueComposite context might be an overkill but this issue arose when I was > following > "HowTo: Create an Entity" (the Accident interface) so I'd like to know what > is your opinion on this matter. > Attached is a simple test app. > Cheers, > Lukasz > _______________________________________________ > qi4j-dev mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/qi4j-dev > > -- 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
