[
https://issues.apache.org/jira/browse/MIME4J-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633218#action_12633218
]
Markus Wiederkehr commented on MIME4J-77:
-----------------------------------------
My concern is mainly that extending a class means establishing an is-a
relationship. And in my opinion a MimeException simply is not an IOException.
That being said it don't think it's a major issue. If I know I have to catch
MimeException before catching IOException then all works well. And users who
don't need to distinguish can simply catch IOException and be done with it.
If you decide to leave it as it is I think the API should properly declare the
MimeException wherever it is thrown. What I mean is a method or constructor
should declare "throws MimeException, IOException" instead of simply declaring
"throws IOException". This can be easily checked by temporarily changing the
super class of MimeException to Exception and running the compiler.
> 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]
