Title: Message
Jason,
 
My brother's working on the validation piece so I'll have him follow up on this. I'm off in Hibernate land until I get a few issues resolved. :-(
 
Thanks,
Peter


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Carreira
Sent: Thursday, October 02, 2003 8:31 AM
To: [EMAIL PROTECTED]
Subject: RE: [OS-webwork] WebWork2 newbie biting off more than I can chew...

Which validators throw exceptions for null Strings? We have the RequiredFieldValidator which checks for null values, and the RequiredStringValidator also checks for empty Strings... The range validators are built to not check fields which are null (assuming you'll have a RequiredFieldValidator if you want to make it required).
 
If you're getting exceptions, it's a bug and we need to fix it.
-----Original Message-----
From: Peter White [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 02, 2003 1:37 AM
To: [EMAIL PROTECTED]
Subject: RE: [OS-webwork] WebWork2 newbie biting off more than I can chew...

Hi Pat,
 
My partner in crime on this project has been experimenting with the validation framework all day. He says it looks like we can do what we want with it with one minor exception (sorry, no pun intended here...) - the validation framework throws an exception if String attributes it's validating are null. It sounds like this might be a bug but we can workaround this by wrapping the String attributes so they return an empty String if they have null values before having them validated. Thanks for the ParameterAware tip, this would definitely be preferable to passing around and working with the request object directly.
 
Regards,
Peter

Reply via email to