To have only one parameter per validator is an interesting idea and no doubt that the current implementation is a big improvement on Tapestry 3, however I do see some loss in flexibility.
One validator in particular that I'm trying to port from Tapestry 3 won't work any more because it requires 3 parameters to be passed to it (one of which was an object, not necessarily a string). I can arrange to get the same result by doing form validation in a listener method, but it certainly was cool to just pass along the needed parameters and not worry about it anymore. Anyway, thanks to all who answered. I appreciate your help to making me understand this better. Denis Souza -----Original Message----- From: Kevin Menard [mailto:[EMAIL PROTECTED] Sent: quinta-feira, 25 de agosto de 2005 19:03 To: Tapestry users Subject: Re: Validator question in Tapestry 4 On Aug 25, 2005, at 4:42 PM, Denis Souza wrote: > Well, making that change gave another exception: "No validator named > 'string' has been defined." I'm pretty sure "string" is the implicit type. If you want it to be something else, you need to use a translator. > I just noticed that all validators present in the Tapestry 4 > framework take > only one property and the property always has the same name as the > validator > itself. Is that a new requirement? I believe this is the case. So each validator does exactly one thing. -- Kevin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
