Ted, scenario:
You have a wizard form bean. You have 5 stages. Each stage is a different
validation. All use the same action mapping and class. Do you really want to
put all 5 validations in the action mapping? I wouldn't BUT... Why not allow
both ways? Either-or thinking is this file or that file, but we can do
and-thinking and allow the developer to choose what best fits his design. I am
+1 for your idea, as long as you allow separate files too.
Paul
Ted Husted <[EMAIL PROTECTED]> wrote: In Struts 1, we put the validators in a
separate file that's tied to
the mappings through the formbean name, or, alternatively, the path.
In Struts 2, we put the validators in a sepaate file that's tied to
the mappings through the classname.
Why is it that we don't make the validators part of the action
mapping, instead of in a separate element?
I wonder if validators should be more like results. (Pre-results, if
you will.) A mapping could have a default validator mapping. If the
mapping is using wildcards, a different validator mapping could be
selected by a wildcard token, or even an interceptor.
I think one reason people find XML configurations hard to use is
because we keep putting tightly-coupled elements in separate files,
instead of saying it all in one place.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------
Yahoo! Music Unlimited - Access over 1 million songs.Try it free.
