Another way to go might be to extend the sample validator application already in the distribution to include an example of validationg a map-backed form, and then attach that to an enchancement ticket.
Hey, here's a nutty idea -- how about validating a HttpRequest?
If we had a validator that could tell us whether the parameters we expected were in the request, and could be converted to the correct type, we might be able to use typed properties on ActionForms.
Right now, we need String properties so that the properties can be validated AND retained for correction. But if
(1) validate the Strings in the HttpRequest, and
(2) teach the tags to check the request if a formbean property is null
then we could use the HttpRequest for an input buffer instead.
Once the HttpRequest passed validation, then we could transfer the parameters to JavaBean properties.
If you're already validating map-backed forms, it seems like a small step to pop the request into a map, and validate that instead =:0)
-Ted.
Max Kremer wrote:
Hi,
I've been working with the validator for several months now and I'd like to make a contribution. My work with the validator has been entirely in Struts and all of my code is Struts related. I've developed a way to validate Map-Backed forms, how can I contribute this code? My code basically consists of a new Validator plugin and new type of validator form.
Max
-- Ted Husted, Struts in Action <http://husted.com/struts/book.html>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
