[
https://issues.apache.org/jira/browse/VALIDATOR-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17907356#comment-17907356
]
Gilles Sadowski commented on VALIDATOR-497:
-------------------------------------------
bq. [...] IBANException. You should be able to distinguish this exception from
others purely based on type to pick the right logic in the catch clause without
hacks like checking exception messages.
+1 if there is a use-case for a "recovery logic"; otherwise, if the only
expected effect is to abort the execution (and, indeed, report a message) then
a standard would do as well (in a "lighter" and more "standard" way).
bq. As to runtime vs checked, it's a little tricky [...] but you could
reasonably go either way.
We already had this conversation, and this "choice" being "tricky" is yet
another example of why checked exceptions are best avoided, in every case.
> Extends validation result of IBANValidator
> ------------------------------------------
>
> Key: VALIDATOR-497
> URL: https://issues.apache.org/jira/browse/VALIDATOR-497
> Project: Commons Validator
> Issue Type: New Feature
> Reporter: Slawomir Jaranowski
> Priority: Major
> Fix For: 1.10.0
>
>
> Currently we have a method {{IBANValidator#isValid}} which return true or
> false depends on validation result.
> But for false result we don't know a reason, which can be like unsupported
> country, invalid pattern, invalid checksum and so on ...
> Proposition is to add next method which throw exception with more details
> about reason of failed verification.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)