Tom,
I've read this thread with great interest.
Currently I'm thinking about the validation problem as well. I looked at
springmodule's Bean validation framework.
(https://springmodules.dev.java.net/docs/reference/0.8/html/validation.html#beanValidator).
Looks quite interesting to me.
Does
]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Validation-Best-Practices--tf4685400.html#a13606501
Sent from the Struts - User mailing list archive at Nabble.com
Tom Schneider wrote:
This is essentially what we're doing as well, but it is far from an ideal
situation. The issue I've seen is that you can't easily use the validators
from the xml in the validate() method. Another disadvantage is that
validation is in 2 different places. Also, some of our
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Validation-Best-Practices--tf4685400.html#a13473039
Sent from the Struts - User mailing list archive at Nabble.com
to define the validation rules.
--
View this message in context:
http://www.nabble.com/Validation-Best-Practices--tf4685400.html#a13477655
Sent from the Struts - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail
validation.(it works in WorkFlowInterceptor).
Sometime, for trivial fields, i can use Struts ValidationFramework.(it
works after ParameterInterceptor)
--
View this message in context:
http://www.nabble.com/Validation-Best-Practices--tf4685400.html#a13453669
Sent from the Struts - User mailing
://www.nabble.com/Validation-Best-Practices--tf4685400.html#a13423610
Sent from the Struts - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hey,
I have a question concerning where validation should be performed, and
what people feel best practices are. Specifically, I have a number of
business objects that validate parameters supplied to their setters
for correctness, and throw IllegalArgumentExceptions if something is
invalid. For
In our application, the implementation for error message handling is: using
a HashMap for error messages with the form propertyName as the key. This
prevents duplicate messages for form fields. Taking one example use-case:
zipCode, rules are: must be numeric, and must be at least 5-digits in
I have a question about the validation in struts.
Imagine that we have:
- jsp page containing the form to be validated
- formbean extending from ValidatorForm
- action to be executed on submit
- validation rules using the validation plugin
If we put the 'validate' attribute to true in the
-
From: Peter Maas [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 08, 2005 5:08 PM
To: Struts Users Mailing List
Subject: validation -- best practices
I have a question about the validation in struts.
Imagine that we have:
- jsp page containing the form to be validated
- formbean extending from
, June 08, 2005 8:28 AM
Subject: RE: validation -- best practices
I also perform client side validation, however what I don't want is
validation BEFORE the user actually got a change to enter data... which
is what happens now...
On Wed, 2005-06-08 at 07:45 -0400, Kalyanasundaram, Arun Sakthi
user@struts.apache.org
To
Struts Users Mailing List user@struts.apache.org
cc
Subject
RE: validation -- best practices
I also perform client side validation, however what I don't want is
validation BEFORE the user actually got a change to enter data... which
is what happens now...
On Wed
Suzanne Rizzo wrote:
I don't know if this is a good practice or not, but my app uses two
entries in struts-config. One with validate=true and one with
validate=false.
I 've never actually used the validate=true in my code; I have an
action superclass that checks for the request type. If
14 matches
Mail list logo
