[
https://issues.apache.org/jira/browse/MIME4J-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633068#action_12633068
]
Oleg Kalnichevski commented on MIME4J-77:
-----------------------------------------
> My estimation is that advanced users working at a low level are more likely
> to care about recovery whereas users working at a high level are unlikely to
> care. So I think that this approach is worthwhile.
Robert et al,
That's the approach we chose for HttpClient 4.0. All core and client components
make a clear distinction between IOExceptions and HttpExceptions. The former
are considered recoverable, the latter are not. At the topmost level (that is,
in the HttpClient class, which is what the overwhelming majority of users are
likely to interact with) HttpExceptions are caught and re-thrown as special
subclass of IOException. All seem happy.
We could make MimeException a separate class of exceptions distinct from
IOException in all low level components and then catch MimeExcetions in the
Message class and rethrow them as IOException.
Oleg
> Decide Whether MimeException should extend IOException
> ------------------------------------------------------
>
> Key: MIME4J-77
> URL: https://issues.apache.org/jira/browse/MIME4J-77
> Project: JAMES Mime4j
> Issue Type: Task
> Affects Versions: 0.4
> Reporter: Robert Burrell Donkin
> Fix For: 0.6
>
>
> Decide whether MimeException should extend IOException
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
