[
https://issues.apache.org/jira/browse/MIME4J-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051232#comment-13051232
]
Oleg Kalnichevski commented on MIME4J-193:
------------------------------------------
MessageFormatterImpl as an implementation of MessageFormatter makes sense to me.
LenientMessageFormatter and StrictMessageFormatter as implementations of
MessageFormatter makes sense to me.
MimeWriter as an implementation of MessageFormatter makes NO sense to me.
MimeWriter implementing MessageFormatter and MimeBuilder NOT implementing
MessageBuilder makes NO sense to me.
Oleg
> Being able to write a message using dom api with no dependencies on the
> message package
> ---------------------------------------------------------------------------------------
>
> Key: MIME4J-193
> URL: https://issues.apache.org/jira/browse/MIME4J-193
> Project: JAMES Mime4j
> Issue Type: Wish
> Components: dom
> Affects Versions: 0.7
> Reporter: Stefano Bagnara
> Fix For: 0.8
>
>
> While refactoring jDKIM against the latest mime4j trunk I found that the code
> now depends on "message" package because of MimeWriter.DEFAULT.writeTo calls.
> At the same time I see we now have MessageServiceFactory.newMessageFormatter
> and MessageFormatter interface that expose a writeTo(Message, OutputStream)
> method: why don't we expose all of the other writeTo methods from MimeWriter,
> too? (and maybe MimeWriter should implement MessageFormatter so we don't need
> the MessageFormatterImpl class at all)
> WDYT?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
