On Tue, Feb 10, 2009 at 2:52 PM, Rickard Öberg <[email protected]> wrote:
> To get this to work there's a bunch of things that needs to be fixed: > * I have set @UseDefaults on a List Property. This would imply creating > an empty ArrayList as default value. Agree. > * I have set @UseDefaults on an enum. This would imply setting it to the > first value in the defined enum. Agree. > * EntityStores have to be able to store hierarchical ValueComposites See http://issues.ops4j.org/browse/QI-174 > * Indexing/querying for all of it. See http://issues.ops4j.org/browse/QI-175 > That should be it. Does this seem like a good way to do it? Viewing this > structure should be straightforward, but I can see that we'd probably > need some way to easily modify the values, or it's going to be rather > tricky... Yes, in principle ok. I think that perhaps the answer is to let the CompositeBuilder prototype to be populated with a value hierarchy in a single call. CompositeBuilder<Phone> builder = ...; PhoneState state = builder.stateFor( PhoneState.class, oldValue ); or something to such extent. Cheers Niclas -- http://www.qi4j.org - New Energy for Java _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
