On 23 June 2011 15:23, Edvin Syse <[email protected]> wrote: > Den 23.06.2011 10:19, skrev Chris Bartlett: > > I haven't looked at the patch, but does it allow java.util.Map values to > also be *set*? If not, the next question on the list will be - 'BeanAdapter > can read value from a java.util.Map, but can't write them' > > Yes ofcourse it allows set as well :)) > > Good stuff.
> Maybe a more flexible solution would be to allow users to control which > class is used to process the TableView.Column.name property? (Defaulting > to BeanAdapter of course). > > > That would allow any custom Map<String, Object> implementation to be > used, giving the user freedom to handle whatever notation they chose. > > I agree, but I think that JSON should support java.util.Map anyways, and > the override for TableView.Colum.name processing could be held off until a > real usecase comes along :) > > -- Edvin > Yep, if your patch sorts things out now, then that is perfect.
