Re: Data validation, mapping, and error handling

I found the JSF validating framework to be quite complex, but apparently

others can make it work well.

I gave up on custom validators and is why I just do the validation in my
controller code. I think custom validators were more for "types of
validation" vs. "business logic validation". For example, if you had a
certain way you wanted users to enter ALL dates on your system then you
would create a custom validator for that, but not if you wanted to test to
see if a customer was over their credit limit.

Aaron Bartell
http://mowyourlawn.com

On Mon, Jun 9, 2008 at 4:08 PM, Thorbjørn Ravn Andersen <
thunderaxiom@xxxxxxxxx> wrote:

Aaron Bartell skrev den 09-06-2008 22:13:

I think it depends on how you look at it. For instance, you are trying

to

use the JSF required="true" parameter to ease your development, but after
learning how that approach works I prefer to simply add an IF statement

in

my handler code to test for the same thing so I can have uniform

validation

(i.e. not have some of it in the UI layer and some in the controller

layer).

You can always let the UI validate stuff like "this should be a valid
number" and "must not be empty", and leave the context dependent
validation to the action called like "This customer do not accept these
kind of deliveries" etc.

I found the JSF validating framework to be quite complex, but apparently
others can make it work well.

--
Thorbjørn
--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.