we should just change our formprocessing traversals to postorder
-igor On 4/24/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
i think it is because you have a panel that is a FormComponent by itself it has 3 textfields and those 3 text fields combines to one thing Then the panel can implement that listener and then it is a FormComponent and will handle all the processing of the 3 textfields thems self. johan On 4/24/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > > Its beeing used for all the 3 steps: > > > > validateRequired(); > > validateConversion(); > > validateValidators(); > > Yes, I've looked at the code of course :) > > > and i guess IFormProcessingListener is the interface of a FormComponent > > So somebody can do there own work in processChildren() > > then return false. So that that Component is seen ans 1 FormComponent > > You guess, and I can guess a couple of use cases myself. However, I'd > like to hear from people actually using it. It looks to me like this > is for supporting some very uncommon use case, that, in case anyone > would actually ever need it, could be done reasonably well in other > ways. > > The interface looks like bloat to me. > > Eelco >
