--- Robert Leland <[EMAIL PROTECTED]> wrote:I agree with this as well, but of course the same concept should apply to all our other configuration information. How many of us have mistyped the name of a form bean class, for example (raises hand :-).
Currently the Validator PlugIn doesnâEUR^(TM)t validate the XML file. I have updated it to remove the deprecated methods and to validate the XML files.
Here is the question: Currently, the validator plugin fails by logging a
message but doesnâEUR^(TM)t take advantage of throwing an exception. I believe
it should throw an exception if the validator file is invalid. Are there
any thoughts or objections to throwing an exception, is that too
incompatable with its current behaviour ?
I agree that we should throw the exception. IMO, it should fail fast and
loud at startup if you've misconfigured the validations.
There was an interesting thread on a similar situation with Hivemind on COMMONS-DEV last week, where those developers seem to believe that users shouldn't want such support ever. I don't agree with that extreme a viewpoint, but it might be nice to make such checks a configuration parameter option (I'd vote for default=true because it probably won't hit startup performance enough to matter for most people).
DavidCraig
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
__________________________________
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway http://promotions.yahoo.com/design_giveaway/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
