Different Annotated Validations for different action methods 2007-12-04 - By Thilo Ettelt
Back
Hey all,
I'm trying to figure out how to validate my action methods differently.
For example I've got a modeldriven User bean with the following two
annotated methods
@(protected)(...)
- processLogin
@(protected)(...)
- processSignup
Now I want the first annotation to only check for the username and
password, but the second annotation is supposed to check for other
things like email too.
However when I call the appropriate action mapping which calls
processSignup it processes both Validations, which results in a
invalid email address error for the login in addition to the wrong
username and password.
So how can I separate the two validatio annotations without needing
separate classes?
- Thilo
--
Mit freundlichen Gr??en,
Thilo Ettelt Telefon: +49-421-6265-111
Carmunity.com GmbH Telefax: +49-421-6265-100
Mary-Astell-Strasse 2 E-Mail: te@(protected)
28359 Bremen http://www.carmunity.de/
Developer (YourVids)
Handelsregisternummer: HRB 19256 beim AG Bremen
Gesch?ftsf?hrer:
Dipl.-Wirt.-Ing. W. Schl?sser
Dipl-Ing. Frank Rothg?nger
Bennet Bock
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To unsubscribe, e-mail: user-unsubscribe@(protected)
For additional commands, e-mail: user-help@(protected)
|
|
