[
https://issues.apache.org/jira/browse/MIME4J-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991991#comment-12991991
]
Oleg Kalnichevski commented on MIME4J-175:
------------------------------------------
Stefano
I personally find it unlikely I will be using MessageBuilderFactory myself
mainly because I _personally_ tend to prefer typed setters over generic
#setProperty that works with Objects. I also tend to prefer a DI based
initialization to that based on a service locator. Having said all that I see
no problem with MessageBuilderFactory being in mime4j. You _should_ try to
bring your work to a logical conclusion of some sort, though. I suspect in some
cases your code 'was not liked' simply because it never felt quite complete.
Oleg
> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
