[MIME4J-156] DOM (message) classes should not be implementation specific. Move implementation to a different package (message.impl)

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.6
• Fix Version/s: 0.7
• Assignee: Stefano Bagnara
• Reporter: Stefano Bagnara
• Created: 31/Dec/09 14:57
• Updated: 14/Mar/10 23:17
• Resolved: 30/Jan/10 21:39

Description

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.

Issue Links

• relates to: MIME4J-175 Introduce a MessageBuilderFactory/MessageBuilder along the lines of DocumentBuilderFactory