I really think that is a good aproach. At least one of the most simple
and centralized. BUT
...from a pure struts point of view someone can think that your
solution is mixing the model with the view.
I think ActionForm should remains as part of the view, or just a 'box'
between the view
Mailing List
Subject: Re: Validations - 'format' vs 'business'
I really think that is a good aproach. At least one of the most simple
and centralized. BUT
...from a pure struts point of view someone can think that your
solution is mixing the model with the view.
I think ActionForm should remains
Guido García Bernardo wrote:
I really think that is a good aproach. At least one of the most simple
and centralized.
Thanks, I take a lot of time to try to KISS.
...from a pure struts point of view someone can think that your
solution is mixing the model with the view.
I think ActionForm
Hi,
I have a design doubt... I must validate data coming from a form. This
consist typically of:
- 'format' validations (i.e. a field is not empty or it is numeric)
that I do in the validate method of the ActionForm
- 'business' validations that usually require a DB access
I actually do 2
{repost}
I just override validate() method on formbean and do all there,
including super.validate() that reads validation.xml. In here I call
DAO's to do business validation also, ex: what is the available credit
for the client to place this order.
Then in action I do this:
errors =
, 2003 10:00 AM
Subject: [OT] Validations - 'format' vs 'business'
Hi,
I have a design doubt... I must validate data coming from a form. This
consist typically of:
- 'format' validations (i.e. a field is not empty or it is numeric)
that I do in the validate method of the ActionForm
6 matches
Mail list logo
