james-mime4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Kalnichevski (JIRA)" <mime4j-...@james.apache.org>
Subject [jira] [Commented] (MIME4J-193) Being able to write a message using dom api with no dependencies on the message package
Date Fri, 17 Jun 2011 09:42:47 GMT

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

Oleg Kalnichevski commented on MIME4J-193:
------------------------------------------

MimeWriter as a specific implementation of MessageFormatter makes no sense to me of what so
ever.

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

        

Mime
View raw message