Paul's solution, in this regard, seems more design consistent.
On 12/18/05, Dakota Jack <[EMAIL PROTECTED]> wrote:
>
> I would think that doing validation in your action would be
> contra-indicated as a design matter, if you are doing Struts struts rather
> than one of the other struts.
>
> On 12/
I would think that doing validation in your action would be contra-indicated
as a design matter, if you are doing Struts struts rather than one of the
other struts.
On 12/18/05, Rick R <[EMAIL PROTECTED]> wrote:
>
> On 12/18/05, Josh McDonald <[EMAIL PROTECTED]> wrote:
> >
> > What's the best plac
Sweet, that's good to know. Not much use in an environment of such
inertia and red tape tho :) I believe it'll be 1.1 for many moons after
my contract is up
--
"His comrades fought beside him, Van Owen and the rest...
But of all the thompson gunners- Roland was the best."
Josh McDona
>>it should be an URL and patch it up (like > 'www.google.com' into
>>'http://www.google.com/').
This is a bug which was fixed in Struts 1.2.8 by upgrading to commons validator
1.1.4.
Paul
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the be
Thanks for your feedback guys, what I've got is some URL validation
(just regexes, nothing magic) but I've also got some smaller regexes to
detect stuff that looks like it should be an URL and patch it up (like
'www.google.com' into 'http://www.google.com/'). For now I've just got
it in the validat
On 12/18/05, Josh McDonald <[EMAIL PROTECTED]> wrote:
>
> What's the best place to put input validation and possible repair?
I actually prefer to do the validation checks in my DispatchAction. The
reason being is that, inevitably, you'll end up with a case where you'll
have some Lists you'll wan
Josh,
You can use a combination of the Commons Validator plus any addition complex
validation in the
validate() method of the action form. No one forces you to use any method.
However, the Commons
Validator is sufficient for 95% of the data validation you need so make sure
you take good
advanta
7 matches
Mail list logo
