james-mime4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Kalnichevski (JIRA)" <mime4j-...@james.apache.org>
Subject [jira] [Resolved] (MIME4J-180) exception expected when mime part has no end boundary and parsing is strict
Date Wed, 15 Jun 2011 14:22:47 GMT

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

Oleg Kalnichevski resolved MIME4J-180.
--------------------------------------

    Resolution: Fixed

Fixed in SVN trunk.

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
>            Assignee: Oleg Kalnichevski
>            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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message