james-mime4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefano Bagnara (JIRA)" <mime4j-...@james.apache.org>
Subject [jira] Resolved: (MIME4J-149) Fix Field, RawField and ParsedField consistency/confustion, dependency hell.
Date Tue, 08 Feb 2011 10:35:57 GMT

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

Stefano Bagnara resolved MIME4J-149.

    Resolution: Fixed

The biggest issue was fixed. So let's mark it as resolved. We can file a new issue to 0.8
when we see how to improve it more.

> Fix Field, RawField and ParsedField consistency/confustion, dependency hell.
> ----------------------------------------------------------------------------
>                 Key: MIME4J-149
>                 URL: https://issues.apache.org/jira/browse/MIME4J-149
>             Project: JAMES Mime4j
>          Issue Type: Task
>    Affects Versions: 0.6
>            Reporter: Stefano Bagnara
>            Assignee: Stefano Bagnara
>            Priority: Minor
>             Fix For: 0.7
> Partially discussed here:
> http://markmail.org/message/7n63uorvnhzqx7mx
> the "new" Field interface creates a bridge between the parser and the rest of the code.
While the bridge could expose potential in fact it expose lack of consistence and unintuitive
interfaces where you don't know if you are dealing with raw fields or parsed fields and some
code ends un parsing already parsed fields.
> Maybe we'll reintroduce a common interface later, but for now I much more prefer to remove
cycles and to have much clearer contracts about what is returne/used by the stream parser
and by the dom.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message