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] Commented: (MIME4J-175) Introduce a MessageBuilderFactory/MessageBuilder along the lines of DocumentBuilderFactory
Date Tue, 08 Feb 2011 10:41:57 GMT

    [ https://issues.apache.org/jira/browse/MIME4J-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991890#comment-12991890

Stefano Bagnara commented on MIME4J-175:

As you can see it was stuck with a proposal in my previous comment. I didn't receive comments
whether it was liked or not so I stopped. I still think that this would be good:
MessageBuilderFactory factory = MessageBuilderFactory.newInstance();
factory.setFeature("strictParsing", true);
factory.setFeature("countLineNumbers", true);
factory.setFeature("malformedHeaderStartsBody", true);
factory.setProperty("maxHeaderLen", 1000);
factory.setProperty("headlessParsing", "multipart/form-data");

as a second step we could expose them as direct properties:

But I'm not sure if I should file a new issue for this or mark this one as rejected. You are
the only one that replied (now) to this and if I understood it you don't like this proposal
and instead prefer people to use MimeEntityConfig, is this right?

> Introduce a MessageBuilderFactory/MessageBuilder along the lines of DocumentBuilderFactory
> ------------------------------------------------------------------------------------------
>                 Key: MIME4J-175
>                 URL: https://issues.apache.org/jira/browse/MIME4J-175
>             Project: JAMES Mime4j
>          Issue Type: Improvement
>          Components: dom
>    Affects Versions: 0.6
>            Reporter: Stefano Bagnara
>            Assignee: Stefano Bagnara
>             Fix For: 0.7
> This factory will support using the dom interfaces without knowledge of the "message"
> Implementing a simple java SPI for the factory will let us to decouple "dom" from "message"
and leave more future extensibility.
> Then we'll have to add body/fields creation methods to Message.
> Message should be traversable and alterable directly from the api.

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


View raw message