You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mime4j-dev@james.apache.org by "Oleg Kalnichevski (JIRA)" <mi...@james.apache.org> on 2010/10/29 11:22:19 UTC
[jira] Commented: (MIME4J-180) exception expected when mime part
has no end boundary and parsing is strict
[ https://issues.apache.org/jira/browse/MIME4J-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926220#action_12926220 ]
Oleg Kalnichevski commented on MIME4J-180:
------------------------------------------
Rohan
Could you please attach a sample file and let me know at what point you would like an exception to be thrown?
Oleg
> exception expected when mime part has no end boundary and parsing is strict
> ---------------------------------------------------------------------------
>
> Key: MIME4J-180
> URL: https://issues.apache.org/jira/browse/MIME4J-180
> Project: JAMES Mime4j
> Issue Type: Improvement
> Affects Versions: 0.6
> Reporter: Rohan Hart
> Priority: Minor
>
> It would simplify my code if, when parsing strictly, the body text stream provided by a mime part would throw an exception, eg., EOFException, when the part has no end boundary. This seems semantically more correct.
> The current behaviour means that I can't just pass the stream but have to wrap it in a proxy which knows about the real stream, the original mime parser and the sequence of events which lead to a check for the end of boundary.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.