>So what do you think on add a property (callable from wtk files) where >we choose the bean property name (translated via reflection to the >right getter call) ?
Can you elaborate on this? You can already set bean properties using WTKX (see the WTKX Primer for more information). Is there something specific you cannot achieve with the existing support? >And last, attention on inserting null values ... could be useful an >event for this, so application could see what to do, or leave the >component work as its defaults. We can't assume that nulls are always invalid (in many cases, they are not). It is up to your bean's setter method to throw an appropriate exception if a null value is passed as an argument.
