[
https://issues.apache.org/jira/browse/MIME4J-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717262#action_12717262
]
Markus Wiederkehr commented on MIME4J-137:
------------------------------------------
IIRC MimeIOException was specifically designed to be an adapter class that
converts a MimeException into an IOException (see MIME4J-77). As a consequence
it should be safe to assume that a MimeIOException always has a cause that is a
MimeException.
Because of this I am not very happy with changing
MimeIOException(MimeException) into MimeIOException(Throwable).
I'm indifferent about the other constructor MimeIOException(String). The stack
trace may become more readable but on the other hand the MimeIOException no
longer has a cause that is a MimeException.
Other opinions?
> Rewrite MimeIOException eliminate unecessary MimeException and provide
> general constructors
> -------------------------------------------------------------------------------------------
>
> Key: MIME4J-137
> URL: https://issues.apache.org/jira/browse/MIME4J-137
> Project: JAMES Mime4j
> Issue Type: Improvement
> Affects Versions: 0.6
> Reporter: Nathan Beyer
> Priority: Minor
> Fix For: 0.7
>
> Attachments: MimeIOException.patch
>
>
> Rewrite the MimeIOException class to eliminate the hidden construction of a
> MimeException and provide a more conventional set of constructors.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
