2011/3/3 Niclas Hedhman <[email protected]>: > The ValueBuilder.withState() calls the provided > StateHolder.visitProperties to build up the content, but it is > non-trivial to get hold of the Properties in the model. Assuming we > would like to keep that as-is for compatibility reasons, I would like > to suggest; > > void dynamically( StateProvider state ); > > public interface StateProvider > { > Object valueFor( PropertyDescriptor descriptor ); > } > > and the ValueBuilder will make a call for each Property to the StateProvider. > > > I use this extensively (the harder way) quite a lot to interact with > all kinds of external systems, where the 'plugin' is given a > ValueComposite type and handed back a populated one... I'll write a > longer mail on that topic. > > WDYT?
If I understand the problem correctly, is it that the callback currently does not get access to the PropertyDescriptor, and only the name? Or is there something else in the current pattern that causes the problems? /Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
