具有生成器模式的Spring@Service逻辑

Question

我已经在Spring Boot应用程序中使用如下构建器模式实现了服务逻辑。

 @Service
public class EmailServiceImpl implements NotificationService{

    private Map<String, Object> emailTemplateContext;;
    private List<String> recipients;
    private String templateName;
    private String subjectName;
    private List<String> ccRecipients;

    public EmailServiceImpl() {
    }

    private EmailServiceImpl(String templateName, String subjectName, List<String> recipients,
            List<String> ccRecipients,
            Map<String, Object> emailTemplateContext) {
        this.emailTemplateContext = emailTemplateContext;
        this.recipients = recipients;
        this.templateName = templateName;
        this.subjectName = subjectName;
        this.ccRecipients = ccRecipients;
    }
    
    public static class EmailBuilder {

        private Map<String, Object> emailTemplateContext = new HashMap<String, Object>();
        private List<String> recipients;
        private String templateName;
        private String subjectName;
        private List<String> ccRecipients;

        public EmailBuilder withTemplateName(String templateName) {
            this.templateName = templateName;
            return this;
        }

        public EmailBuilder withSubjectName(String subjectName) {
            this.subjectName = subjectName;
            return this;
        }

        public EmailBuilder withTemplateContextValues(String key, String value) {
            this.emailTemplateContext.put(key, value);
            return this;
        }
        
        public EmailBuilder withTemplateContextValues(String key,List< String> value) {
            this.emailTemplateContext.put(key, value);
            return this;
        }

        public EmailBuilder withRecipients(List<String> recipients) {
            this.recipients = recipients;
            return this;
        }

        public EmailBuilder withCCRecipients(List<String> ccRecipients) {
            this.ccRecipients = ccRecipients;
            return this;
        }

        public EmailServiceImpl build() {
            return new EmailServiceImpl(templateName, subjectName, recipients, ccRecipients, emailTemplateContext);
        }
    }
    
    public void send() {
     // implement email send logic
    }
}

然后这将被注入另一个类中，如下所示

 public class EmailSender{
private EmailBuilder emailBuilder;
    EmailSender(EmailBuilder emailBuilder){
     this.emailBuilder=emailBuilder;
}

public void sendEmail(){
                this.emailBuilder
                .withRecipients(executionRunBO.getEmailRecipients().stream().map(email -> email.getEmail())
                        .collect(Collectors.toList()))
                .withSubjectName("Reports Draft ").withTemplateName("/emails/reports.ftlh")
                .withTemplateContextValues("userName", "TestUser").build().send();

}
}

与Spring的Builder模式相关的问题很少。

>

如何从服务类外部调用EmailServiceImpl类的EmailBuilder？因为在我的示例中，我已经将EmailBuilder作为构造函数参数注入，然后Spring框架抛出了它

需要类型为“”的bean。。。找不到EmailServiceImpl$EmailBuilder。

请帮我澄清那些事情。

Answer 1

你在这里混合了很多功能。我会让它更精简。

我会创建一个dto类Email，而不是Spring bean。

public class Email {
    private Map<String, Object> emailTemplateContext;
    private List<String> recipients;
    private String templateName;
    private String subjectName;
    private List<String> ccRecipients;

    private Email(String templateName, String subjectName, List<String> recipients,
                             List<String> ccRecipients,
                             Map<String, Object> emailTemplateContext) {
        this.emailTemplateContext = emailTemplateContext;
        this.recipients = recipients;
        this.templateName = templateName;
        this.subjectName = subjectName;
        this.ccRecipients = ccRecipients;
    }

    public static class EmailBuilder {
        // your builder code, just build the Email 
    }

}

然后有一个发送电子邮件的服务。

@Service
public class EmailServiceImpl implements NotificationService {
    
    public void sendEmail(Email email) {
        
    }

}

像这样叫它

emailService.sendEmail(new Email.EmailBuilder().build());

无需从电子邮件和电子邮件生成器创建服务。