Mailing-List: contact mime4j-dev-help@james.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mime4j-dev@james.apache.org
Date: Fri, 17 Jun 2011 08:44:47 +0000 (UTC)
From: "Stefano Bagnara (JIRA)" <mime4j-dev@james.apache.org>
To: mime4j-dev@james.apache.org
Message-ID: 
 <102899652.14223.1308300287538.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <455698579.63101.1303038245845.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (MIME4J-193) Being able to write a message using
 dom api with no dependencies on the message package
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Stefano Bagnara commented on MIME4J-193:
----------------------------------------

With minor changes to MessageFormatter I'm now able to use mime4j from jDKIM without knowing the "message" package.

I still have to use the "stream" package for MimeEntityConfig and the "new" Field.

I don't expect we can find an easy agreement in the short term about refactoring the code (so that I don't need the stream package visibility when doing dom manipulation), so I prefer to leave this part of the issue planned for 0.8 and to not delay 0.7 release.

> 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