Hi John (and Mitch)! Did this patch ever get committed? http://archives.apache.org/eyebrowse/ReadMsg?listName=turbine-user@;jakarta.apache.org&msgNo=10231
I am pretty sure it solves the problem Mitch is describing, but I could be wrong... Regards, -- Rodney On Wed, 23 Oct 2002 11:20, you wrote: > I think I've found the problem. > > During field validation, Field.validate() calls > DefaultValidator.assertValidity() (Field:450) for the field in question, > passing in the candidate value (from the form). Inside > DefaultValidator.asserValidity() a test is made for value length > (DefaultValidator:213). My value fails this test (it's too short), so the > 'message' is set the 'minLengthMessage' (DefaultValidator:215). The a new > ValidationException is thrown (DefaultValidator:216). This exception is > caught by Field.validate() (Field:457). Unfortunately, this bypasses the > (overidden) StringField.doSetValue(pp) call on line 454. As such, > setTestValue() never gets called, and Field.testValue never get set, > resulting in no value being displayed back in your form. > > Now, the question is, what do I do about this? I suppos that I could not > use the IntakeService, but I would *really* like to. An obvious > alternative would be to fix/patch locally. I'm not sure how much time that > would take, I've never compiled Turbine before. > > Any other suggestions? > > -Mitch > > PS It would be nice if someone would be kind enough to validate/invalidate > my findings in case I'm totally wrong on this one. -- To unsubscribe, e-mail: <mailto:turbine-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:turbine-user-help@;jakarta.apache.org>
