That looks like an interesting project. There are a lot of things that I
like about what they are doing. There are a lot of things that could be
handle that way. My fear with making everything a seperate Rule class is
that some things cannot be encoded as a simple rule. Somevalidation needs
to
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 som
Just wanted to point out: http://jcp.org/en/jsr/detail?id=303 which is
relevant to our discussion. No activity on this JSR since July of '06. I'm
not convinced that annotations really solve the problem. I think for
anything more than simple type checking you need a true programming language
to
I think drools would be way overkill for simple validation. Not only would
there be a high learning curve, I don't think it would handle the most
involved cases. I really think we need to do Java by default.
The reason I included a way to autofind the validation class is to mimic how
the existi
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 v
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 validate() methods
get
I use validate() method from ActionSupport for complex bussines
validation.(it works in WorkFlowInterceptor).
Sometime, for trivial fields, i can use Struts ValidationFramework.(it
works after ParameterInterceptor)
Sean Kleinjung-2 wrote:
>
> Hey,
>
> I have a question concerning where val
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 typ
8 AM
Please respond to
"Struts Users Mailing List"
To
Struts Users Mailing List
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
nt: Wednesday, 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, Kalyanasun
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
(Cognizant) wrote:
> Hi Peter,
>
> The validation that is basically p
Hi Peter,
The validation that is basically performed in the approach you have
specified is client side validation.
Please elaborate more why you want to make a server hit before the data
is validated and corrected in Client side itself.
Thanks and Regards,
Arun Sakthi
-Original Message-
12 matches
Mail list logo
