Mailing-List: contact mime4j-dev-help@james.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mime4j-dev@james.apache.org
Message-ID: <2052553085.1244475008569.JavaMail.jira@brutus>
Date: Mon, 8 Jun 2009 08:30:08 -0700 (PDT)
From: "Stefano Bagnara (JIRA)" <mime4j-dev@james.apache.org>
To: mime4j-dev@james.apache.org
Subject: [jira] Commented: (MIME4J-137) Rewrite MimeIOException eliminate
 unecessary MimeException and provide general constructors
In-Reply-To: <179780491.1244428807711.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/MIME4J-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717298#action_12717298 ] 

Stefano Bagnara commented on MIME4J-137:
----------------------------------------

I agree with Markus.

Stack traces should be shortened in the code that intercept exceptions, not in the library itself.

The idea of MimeIOException is that we needed to throw a MimeException in methods supporting only IOException. Using the current "cause" way let the mime4j users to get access to check and get access to the underlying mimeexception when they care to.


> 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.