You should look at my attached snipped more closely. ;) I implemented your EXACT ValidatorLIst interface. That means that no code was changed anywhere else and when there's no validator, there's no reference, when there's one, there's no list. Exactly the same, except that validation occures in the order the components were added.
On 8/11/05, Jonathan Locke <[EMAIL PROTECTED]> wrote: > > nope. look at the code more closely. when there's only one validator, > there's > no validator list. it's exactly like the multicaster hack we threw in > there in awt > and swing for the same reason... > ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
