It's not common practice to put business-data validation in the form beans
validate method, since this belongs in the data object (or
controller/service tier), so you should move that into the action class or
data object classes, and then you can use the database to update and
retrived login atte
The best thing is to think of the ActionForm as a data transfer object.
As such, it shouldn't be accessing the data service itself, but simply
carrying the data for others to use.
The validate method is an apology to the web tier. The standard HTML
controls will accept any String value you car
hope this helps,
Mike
- Original Message -
From: "Cohan, Sean" <[EMAIL PROTECTED]>
To: "'Struts Users Mailing List'" <[EMAIL PROTECTED]>
Sent: Friday, September 06, 2002 9:19 AM
Subject: DB hit from ActionForm Validate method
> We need to i
Sean,
-- My question is whether it is acceptable or common practice to
> access the DB from the validate method or should DB access only be done in
> the LogonAction class (which means I'd move the perform functionality to
the
> LogonAction class)?
--
IMHO, the answer is: logins are DB functi
: 'Struts Users Mailing List'
Subject: DB hit from ActionForm Validate method
We need to implement '3 strikes and your out' functionality to our logon
process. If the user is unsuccessful after 3 logon attempts, we disable
their account. I put some of the user id / password
We need to implement '3 strikes and your out' functionality to our logon
process. If the user is unsuccessful after 3 logon attempts, we disable
their account. I put some of the user id / password functionality in the
validate method of the LogonForm class. However, in between each attempt, I
n
6 matches
Mail list logo