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 Mon, 15 Mar 2010 00:01:27 GMT

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

Stefano Bagnara commented on MIME4J-175:
----------------------------------------

The same pattern could be used to obtain the FieldParser (so to remove direct DefaultFieldParser.parse
calls)

Also we could use the same logic and create a MessageParserFactory/MessageParser so that we
can use MessageBuilder+MessageParser to build a message from a stream.

> 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"
package.
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message