On Friday 25 October 2002 07:07 pm, Stephen Colebourne wrote: > Other object models that could be considered: > JAXB > Swing > neither strike me as essential. > > However, providing base support for Map properties in beans seems essential > to me. We should support beans with simple (atomic) properties, array > properties, List properties and Map properties. The act of deciding what is > an SimpleArray/ListMap property (ie. what the methods are what etc. is > pluggable) > Perhaps we should take a view of eventually proposing a JSR for it. The fact that the java bean spec doesn't address collection properties means that everyone creates their own, similar, workarounds.
I think a good aproach for pluggability is the BeanInfo class. It's well defined how to create a BeanInfo that overides the default java bean behavior. In fact, that's one of the reasons you have to use Introspection to deal with javabeans correctly. There is a lot to critisise about the BeanInfo spec, though. The loose coupling between a BeanInfo and it's class has resulted in genuine java bugs, for example. Hejlsberg's approach of requiring an inner class has some advantages. -- To unsubscribe, e-mail: <mailto:commons-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:commons-dev-help@;jakarta.apache.org>
