On 5/8/06, Ittay Dror <[EMAIL PROTECTED]> wrote:
only if there is a compound model up the hiearchy AND you create the components inside the aggregator w/out a model - which of course you shouldnt do if you are putting them in there
Igor Vaynberg wrote:
> but you can make it generic pretty easily:
>
> class AggreatingAtomicFormComponent extends FormComponent {
>
>
> updateModel() {
> visitChildren(new FormComponent.IVisitor() { ... updatemodel(); });
the sub components will try to use their ancesstor's model, and set the object there, which will probably fail.
only if there is a compound model up the hiearchy AND you create the components inside the aggregator w/out a model - which of course you shouldnt do if you are putting them in there
-Igor
