-1 Client side validation is disabled by default in Tapestry 3. When I port it would be nice not to have to add something to every @Form to maintain the current application behaviour.
Geoff On 9/22/05, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > Thanks to Paul Ferraro, server- and client-side input validation in > Tapestry 4 is back to being best of breed. The question is ... is it > good enough that client validation should be enabled by default? > > In Tapestry 4.0, the Form component now has a clientValidationEnabled > parameter that default to false. > > I feel that it should default to true, as long as the Form is enclosed > by a Body component. > > Are there cases where you *don't* want client validation enabled? > > -- > 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] > > -- The Spindle guy. http://spindle.sf.net Get help with Spindle: http://lists.sourceforge.net/mailman/listinfo/spindle-user Announcement Feed: http://www.jroller.com/rss/glongman?catname=/Announcements Feature Updates: http://spindle.sf.net/updates --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
