[
https://issues.apache.org/jira/browse/TAP5-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12838051#action_12838051
]
Thiago H. de Paula Figueiredo commented on TAP5-1032:
-----------------------------------------------------
Couldn't we use the approach of creating a Translator and Validator
subinterfaces and adding the improved method signatures on them?
> Reporting validation exceptions by throwing an exception is bad form: allow
> for returning a value instead
> ---------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1032
> URL: https://issues.apache.org/jira/browse/TAP5-1032
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.2.0
> Reporter: Howard M. Lewis Ship
>
> From the Dept. Of "We did this in T4 and didn't know it was brain damaged
> then." ... various APIs related to translation and validation work by
> throwing a ValidationException which is nothing more than a wrapper around an
> error message string. It would be nice to allow, in some compatible way,
> allow methods to simply return the exception, or even just the string for the
> exception, rather than throwing an exception, which is very inefficient.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
