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'
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. If beneficial, this could be extended to cover all other Components which use BeanAdapter internally, or even to have a system property/ApplicationContext property/static Component property to specify a global 'BeanAdapterFactory'. Chris On 23 June 2011 14:42, Sandro Martini <[email protected]> wrote: > Hi Edvin, > the patch seems good (I like this feature, improving interaction with > domain > objects is important), would you like to reopen the issue > https://issues.apache.org/jira/browse/PIVOT-764 > and attach the patch there (maybe deleting the old one ...) ? > > So if Greg is not against this we can apply it. > > Bye > > > -- > View this message in context: > http://apache-pivot-users.399431.n3.nabble.com/No-support-for-Map-in-BeanAdapter-tp3097003p3098900.html > Sent from the Apache Pivot - Users mailing list archive at Nabble.com. >
