I would say: just subclass FormAction and redefine either
validate(RequestContext, Object, Errors) or invokeValidatorMethod(String,
Object, Errors). Typically you could do that in a custom FormAction base
class that you use for all form actions in your project.
Erwin Vervaet
----- Original Message -----
From: "Steven Devijver" <ste...@gm...>
To: <spr...@li...>
Sent: Thursday, April 21, 2005 9:39 AM
Subject: [Springframework-developer] webflow: validator invocation strategy
Hi guys,
You recently extended validator invocation functionality in Web Flow
by calling a specific method on a validator instance. I propose to
make this behavior more generic. While I think calling a specific
method on the validator is a great way to do validation across
multiple pages there's a comparable strategy I would like to see
implemented.
I would like to call a collection of validators linked to a specific
string token in a map. The string token would be the equivalent of a
method name and would be defined in the flow config.
In order to implement this I propose to call specific validator
invocations through an interface that would allow different strategies
to be implemented.
Kind regards
Steven
--
"If you want to be a different fish, you gotta jump out of the school."
-- Captain Beefheart
-------------------------------------------------------
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer
|
