[
https://issues.apache.org/jira/browse/MIME4J-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski updated MIME4J-180:
-------------------------------------
Fix Version/s: 0.7
Fair enough. I'll try to come up with a fix in the coming days.
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
> Fix For: 0.7
>
> Attachments: TuncTest.java
>
>
> 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.
