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 "Stefano Bagnara (JIRA)" <mi...@james.apache.org> on 2009/12/30 16:08:29 UTC
[jira] Created: (MIME4J-155) MimeEntity should receive a new
MutableBodyDescriptor for its body, and not receive the optional parent.
MimeEntity should receive a new MutableBodyDescriptor for its body, and not receive the optional parent.
--------------------------------------------------------------------------------------------------------
Key: MIME4J-155
URL: https://issues.apache.org/jira/browse/MIME4J-155
Project: JAMES Mime4j
Issue Type: Improvement
Affects Versions: 0.6
Reporter: Stefano Bagnara
Assignee: Stefano Bagnara
Priority: Minor
Fix For: 0.8
If we change MimeEntity to receive the MutableBodyDescriptor to be used in that entity instead of passing the parent (or null for the first one) then we can later give people more flexibility providing their own BodyDescriptor implementation.
In order to allow MimeEntity to create child instances of itself we also have to add to the MutableBodyDescript a newChild() method that creates a new child instance of itself.
This remove the knowledge of MutableBodyDescriptor implementations (Default/Maximal) from all parser classes but the MImeTokenStream and later we can try to also remove the class knowledge from there and leave it only in a default parser facility.
This will make it much more simple to let parser and field be not dependant on each other.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (MIME4J-155) MimeEntity should receive a new
MutableBodyDescriptor for its body, and not receive the optional parent.
Posted by "Stefano Bagnara (JIRA)" <mi...@james.apache.org>.
[ https://issues.apache.org/jira/browse/MIME4J-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefano Bagnara resolved MIME4J-155.
------------------------------------
Resolution: Fixed
Merged from cycleclean branch.
> MimeEntity should receive a new MutableBodyDescriptor for its body, and not receive the optional parent.
> --------------------------------------------------------------------------------------------------------
>
> Key: MIME4J-155
> URL: https://issues.apache.org/jira/browse/MIME4J-155
> Project: JAMES Mime4j
> Issue Type: Improvement
> Affects Versions: 0.6
> Reporter: Stefano Bagnara
> Assignee: Stefano Bagnara
> Priority: Minor
> Fix For: 0.7
>
>
> If we change MimeEntity to receive the MutableBodyDescriptor to be used in that entity instead of passing the parent (or null for the first one) then we can later give people more flexibility providing their own BodyDescriptor implementation.
> In order to allow MimeEntity to create child instances of itself we also have to add to the MutableBodyDescript a newChild() method that creates a new child instance of itself.
> This remove the knowledge of MutableBodyDescriptor implementations (Default/Maximal) from all parser classes but the MImeTokenStream and later we can try to also remove the class knowledge from there and leave it only in a default parser facility.
> This will make it much more simple to let parser and field be not dependant on each other.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.