You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Robert Burrell Donkin (JIRA)" <se...@james.apache.org> on 2008/09/20 12:51:44 UTC

[jira] Deleted: (MIME4J-76) Should MimeException extent IOException

     [ https://issues.apache.org/jira/browse/MIME4J-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Burrell Donkin deleted MIME4J-76:
----------------------------------------


> Should MimeException extent IOException
> ---------------------------------------
>
>                 Key: MIME4J-76
>                 URL: https://issues.apache.org/jira/browse/MIME4J-76
>             Project: JAMES Mime4j
>          Issue Type: Bug
>            Reporter: Markus Wiederkehr
>
> The constructor of Message(InputStream) uses its inner class MessageBuilder to parse the input stream and create the object. The method MessageBuilder.field(String) calls Field.parse(String) to parse header fields. This method throws an IllegalArgumentException on parse errors.
> Clearly the Message constructor should throw a MimeException instead of an IllegalArgumentException if an invalid header field is encountered (or else it should simply ignore the field). So either Field.parse(String) should throw a MimeException or MessageBuilder.field(String) should catch and convert it.
> And by the way, could you make MessageBuilder public so it can be extended if a slightly different behavior is desired.

-- 
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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org