Great! I've barely gotten most of the unit tests working again. (all besides the TemplateParser tests, but I think the matching line numbers are a cross-platform issue)
I will attack this soon, still adding in the JSON render into the response cycle right now. (possibly thinking about adding in your EventListener annotation as well ) On 3/15/06, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > > The ValidField component should go, and its the only thing that uses > these validators. > > Paul's new validation framework is in the tapestry.form.validiators > and tapestry.form.translators packages (from memory). > > There's also a validator: binding prefix that should go. > > On 3/12/06, Jesse Kuhnert <[EMAIL PROTECTED]> 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 > > > > > > > -- > Howard M. Lewis Ship > Independent J2EE / Open-Source Java Consultant > Creator, Jakarta Tapestry > Creator, Jakarta HiveMind > > Professional Tapestry training, mentoring, support > and project work. http://howardlewisship.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
