[
https://issues.apache.org/jira/browse/MIME4J-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefano Bagnara resolved MIME4J-156.
------------------------------------
Resolution: Fixed
Merged from cycleclean branch. Created MIME4J-172, MIME4J-171, MIME4J-170,
MIME4J-169 for the tasks/pending things discussed in the last comment.
> DOM (message) classes should not be implementation specific. Move
> implementation to a different package (message.impl)
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: MIME4J-156
> URL: https://issues.apache.org/jira/browse/MIME4J-156
> Project: JAMES Mime4j
> Issue Type: Improvement
> Affects Versions: 0.6
> Reporter: Stefano Bagnara
> Assignee: Stefano Bagnara
> Fix For: 0.7
>
> Attachments: graph-mime4j-package.png
>
>
> Let's start "splitting" message between generic interfaces/abstract classes
> and specific implementations based on mime4j modules (parser).
> Abstract classes vs Interface is a tricky issue wrt api. I think the
> important thing now is to separate implementation details from design/api.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
