You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mime4j-dev@james.apache.org by "Ioan Eugen Stan (JIRA)" <mi...@james.apache.org> on 2013/03/11 12:51:15 UTC
[jira] [Commented] (MIME4J-222) MessageImplFactory is needed
[ https://issues.apache.org/jira/browse/MIME4J-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13598750#comment-13598750 ]
Ioan Eugen Stan commented on MIME4J-222:
----------------------------------------
Thank you, I will take care of it.
> MessageImplFactory is needed
> ----------------------------
>
> Key: MIME4J-222
> URL: https://issues.apache.org/jira/browse/MIME4J-222
> Project: James Mime4j
> Issue Type: Improvement
> Components: parser (core)
> Affects Versions: 0.8
> Reporter: Raman Gupta
> Assignee: Ioan Eugen Stan
> Fix For: 0.8
>
> Attachments: mime4j-222.patch
>
>
> In order to create a custom Message-Id, one must currently override the method "newMessageId" e.g.
> return new MessageImpl() {
> @Override
> protected UnstructuredField newMessageId(String hostname) {
> String fieldValue = createUniqueMessageId(hostname);
> return parse(UnstructuredFieldImpl.PARSER, FieldName.MESSAGE_ID, fieldValue);
> }
> };
> However, in some cases Mime4j instantiates the MessageImpl internally e.g. DefaultMessageBuilder.parseMessage and therefore the newMessageId function cannot be overwridden. This means that I cannot use DefaultMessageBuilder to create a MessageImpl in which I control how the Message-Id is created.
> I have attached a patch to make DefaultMessageBuilder take a MessageImplFactory to create the MessageImpl.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira