You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by bu...@apache.org on 2004/06/22 16:58:51 UTC
DO NOT REPLY [Bug 29736] -
ValidatorForm.validate should be able to throw ValidatorException
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=29736>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=29736
ValidatorForm.validate should be able to throw ValidatorException
Joe@Germuska.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
Summary|ValidatorForm.validate |ValidatorForm.validate
|should be able to throw |should be able to throw
|ValidatorException |ValidatorException
------- Additional Comments From Joe@Germuska.com 2004-06-22 14:58 -------
ValidatorException is a checked exception, which means it would need to be added to the interface for
ActionForm, breaking backwards compatibility with all existing ActionForm implementations, many of
which don't even use Commons Validator.
Arguably, we could create o.a.struts.validator.ValidatorException as a subclass of RuntimeExtension
and throw that, but still, it would disrupt a lot of existing code to start throwing exceptions someplace
where they were previously being caught.
In the meantime, you could throw a different runtime exception from your custom plugin, or do that
part of the validation in the action instead of in form.validate().
We couldn't fix this without a suggestion for a less disruptive way to handle it than changing the
signature of ActionForm.validate()
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org