zoukankan      html  css  js  c++  java
  • [Spring Pattern] Builder pattern

    First, let's see the code:

    // builder/Contact.java
    
    public class Contact {
        private String firstName;
        private String lastName;
        private String emailAddress;
    
        public Contact() {
            super()
        }
    
        public String getFirstName() {
            return firstName;
        }
    
        public void setFirstName(final String firstName) {
            this.firstName = firstName;
        }
    
        public String getLastName() {
            return lastName;
        }
    
        public void setLastName(final String lastName) {
            this.lastName = lastName;
        }
    
        public String getEmailAddress() {
            return emailAddress;
        }
    
        public void setEmailAddress(final String emailAddress) {
            this.emailAddress = emailAddress;
        }
    }

    Using it:

        @GetMapping("presidents")
        public List<Contact> getPresidents() {
            List<Contact> contacts = new ArrayList<>();
    
            Contact contact = new Contact();
            contact.setFirstName("George");
            contact.setLastName("Washington");
            contacts.add(contact);
    
            contacts.add(new Contact("John", "Adams", null));
    
            return contacts;
        }

    For the highlighted part, there are two ways to create contact object.

    One is multi lines:

            Contact contact = new Contact();
            contact.setFirstName("George");
            contact.setLastName("Washington");
            contacts.add(contact);

    Another way is single line:

    contacts.add(new Contact("John", "Adams", null));

    The problems are 1. too much line of code when object get complex; 2. The order of params you need to rememeber.

    Builder pattern:

    public class ContactBuilder {
        private String firstName;
        private String lastName;
        private String emailAddress;
    
        public ContactBuilder setFirstName(final String firstName) {
            this.firstName = firstName;
            return this;
        }
    
        public ContactBuilder setLastName(final String lastName) {
            this.lastName = lastName;
            return this;
        }
    
        public ContactBuilder setEmailAddress(final String emailAddress) {
            this.emailAddress = emailAddress;
            return this;
        }
    
        public Contact buildContact () {
            return new Contact(firstName, lastName, emailAddress);
        }
    }

    Keep returning 'this' to enable chaining method calls. 

    Using it:

        @GetMapping("presidents")
        public List<Contact> getPresidents() {
            List<Contact> contacts = new ArrayList<>();
    
            Contact contact = new Contact();
            contact.setFirstName("George");
            contact.setLastName("Washington");
            contacts.add(contact);
    
            contacts.add(new Contact("John", "Adams", null));
    
            // using ContactBuilder
            contacts.add(
                    new ContactBuilder()
                            .setFirstName("Thomas")
                            .setLastName("Jefferson")
                            .buildContact()
            )
            return contacts;
        }

    When to use this pattern:

    1. Useful when object creation has many parameters

    2. Becomes increasingly more useful when some or all parameters are optional

    3. Can make code easier to read because of reduced lines for construction when compared with setters

  • 相关阅读:
    On the fly test
    Spec Explorer 工具学习
    C# Static修饰符的作用
    [转]C#静态方法与非静态方法的比较
    如何获取网站服务器运行状态
    C#快速整理代码格式
    UI auto程序结构组织方式
    TestClass必须是public的
    VS2012如何显示行号
    Error: member names cannot be the same as their enclosing type
  • 原文地址:https://www.cnblogs.com/Answer1215/p/13969683.html
Copyright © 2011-2022 走看看