Also, I forgot to mention, I'd like to avoid the use of "Error" when
referring to messages, because many times there are errors,
warnings, and information messages. I like the ability for
validation to raise warnings that don't result in a failure, but
allows me to warn the user the value might not be what they were
intending.
How do you envision that working? Would individual messages have an
optional "severity" property? (i.e. "error", "warning", possibly
others) Or would there be one bundle of messages for each severity?
I've taken to using a generic BusinessProcessResult object (sometimes
extended with process-specific details) which carries with it three
lists messages: "message," "warning," and "error". (Actually, it can
have other lists with arbitrary keys, but those three have
"privileged" status in the API.)
For our purposes, it could be a "ValidationResult" which gets passed
around through the different validators, each of which can add to any
of the lists as appropriate.
Seems like something which people might not like as a matter of
taste, but I've found it pretty handy. It's also a bigger model
change from both Struts and Webwork than may be appropriate at this
time.
In short, I think it's nice to have a "warning" level if we can work
out a clean way to support it.
Joe
--
Joe Germuska
[EMAIL PROTECTED] * http://blog.germuska.com
"You really can't burn anything out by trying something new, and
even if you can burn it out, it can be fixed. Try something new."
-- Robert Moog
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
