[OFBIZ-4333] Refactoring send email engine

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: Trunk
• Fix Version/s: Trunk
• Component/s: ALL COMPONENTS, content, framework
• Labels: content mail notification
• Assignee: Unassigned
• Reporter: Nicolas Malin
• Created: 07/Jul/11 08:11
• Updated: 13/Dec/11 15:15
• Resolved: 26/Jul/11 09:15

Description

In OFBiz history, the first entity used was ProductStoreEmailSetting, for automatic email during ecommerce process and in last time the EmailTemplateSetting for specific notification.

Both entities have the same field : bodyScreenLocation, xslfoAttachScreenLocation, fromAddress, ccAddress, bccAddress, subject, contentType. Just primary key are differents.

To simplify the notification system, I will suggest :

• use only EmailTemplateSetting to edit email configuration
• associate ProductStoreEmailSetting to EmailTemplateSetting
• convert all service and screen that use ProductStoreEmailSetting
• create convert service.
• add contentId on EmailTemplateSetting (or templaceContentId) to use a content for rendering email