Ok will do. I've temporarily refactored enough to make the old validators work again, but have my sights set on destroying them as soon as makes sense. Still a lot of other things that need to be put in place before I'm ready to attack the form logic.
On 3/13/06, Paul Ferraro <[EMAIL PROTECTED]> wrote: > > +1 > > We should first make sure that each valid.IValidator has a functionally > equivalent form.validator.Validator. > e.g. I don't think the URLValidator was ever ported... > > Paul > > Jesse Kuhnert wrote: > > In the process of cleaning up a couple core interfaces > > (IEngine/IRequestCycle/IPage/etc...) it is now not possible to get the > > IScriptSource from the engine (as it is injectable). > > > > This has made most of the validators in org.apache.tapestry.valid more > or > > less not working... > > > > I'm wondering if it's worth the effort to refactor everything to work > with > > these or if org.apache.tapestry.form.validator is not meant to replace > them? > > > > > > I think this causes a vast amount of confusion for a lot of people and > I'd > > personally like to axe one or the other. Along with ValidField and any > other > > components that aren't relevant anymore. > > > > ? > > jesse > > > > > > > >
