james-mime4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefano Bagnara (JIRA)" <mime4j-...@james.apache.org>
Subject [jira] Created: (MIME4J-155) MimeEntity should receive a new MutableBodyDescriptor for its body, and not receive the optional parent.
Date Wed, 30 Dec 2009 15:08:29 GMT
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.


Mime
View raw message