Yes, the functionality is there. But it actually caused some problems on the Struts side and I think I need to roll back StrutsValidator.java to use booleans again. With it returning the actual value, you can't indicate that it should still continue with other validations if you would want it to skip a specific validation for some reason. The only other solution I can think of is to return a validator specific object that could contain the boolean result and the converted value. Or run the validation rules once against boolean values and again against the ones that return the correctly typed object. Hope that makes sense.
David --- Ted Husted <[EMAIL PROTECTED]> wrote: > Craig R. McClanahan wrote: > > >>Another common approach is an attempt to optimize > things by performing the > conversion only once, in the validate() method of > the form bean. It goes > something like this for an integer property named > foo:<< > > <snip/> > > David, did we ever implement the Validator "type > cache" feature, where > it would add a validated type to a Map? > > In most cases, the Validator actually does the type > conversion to > validate the data. The idea was that it should then > store the converted > value in a Map where an Action could get at it > later. So, we get both > validation and conversion in the same standard, easy > to use package :0) > > -Ted. > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > __________________________________________________ Do You Yahoo!? HotJobs - Search Thousands of New Jobs http://www.hotjobs.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
