[
https://issues.apache.org/jira/browse/IO-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12555790#action_12555790
]
Jukka Zitting commented on IO-148:
----------------------------------
No worries about the svn copy, I'm not too attached on my version of the class.
:-)
IOExceptionWithCause sounds good. With CauseIOException I was trying (clumsily,
I admit) to keep the class name as a kind of a compound word.
ExtendedIOException would also work, but IOExceptionWithCause is more accurate.
I'm with Gary on that a String-only constructor is not needed. In fact it might
even be worth it to enforce that such an exception always comes with a non-null
root cause exception.
> IOException with constructors which take a cause
> ------------------------------------------------
>
> Key: IO-148
> URL: https://issues.apache.org/jira/browse/IO-148
> Project: Commons IO
> Issue Type: New Feature
> Reporter: Niall Pemberton
> Priority: Minor
> Fix For: 1.4
>
>
> Add an IOException implementation that has constructors which take a cause
> (see TIKA-104). Constructors which take a cause (Throwable) were not added to
> IOException until JDK 1.6 but the initCause() method was added to Throwable
> in JDK 1.4.
> We should copy the Tika implementation and test case here:
> http://svn.apache.org/repos/asf/incubator/tika/trunk/src/main/java/org/apache/tika/exception/CauseIOException.java
> http://svn.apache.org/repos/asf/incubator/tika/trunk/src/test/java/org/apache/tika/exception/CauseIOExceptionTest.java
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
