Package org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.bmp.monitor.config.rev200120.server.config

Class ServerBuilder

  • All Implemented Interfaces:
    org.opendaylight.yangtools.concepts.Builder<Server>, org.opendaylight.yangtools.concepts.CheckedBuilder<Server,​IllegalArgumentException>, org.opendaylight.yangtools.concepts.Mutable, org.opendaylight.yangtools.concepts.MutationBehaviour<org.opendaylight.yangtools.concepts.Mutable>
    @Generated("mdsal-binding-generator")
public class ServerBuilder
extends Object
implements org.opendaylight.yangtools.concepts.Builder<Server>
    Class that builds Server instances. Overall design of the class is that of a fluent interface, where method chaining is used.

    In general, this class is supposed to be used like this template: 

       
     Server createServer(int fooXyzzy, int barBaz) {
         return new ServerBuilder()
             .setFoo(new FooBuilder().setXyzzy(fooXyzzy).build())
             .setBar(new BarBuilder().setBaz(barBaz).build())
             .build();
     }

    This pattern is supported by the immutable nature of Server, as instances can be freely passed around without worrying about synchronization issues.

    As a side note: method chaining results in:

    • very efficient Java bytecode, as the method invocation result, in this case the Builder reference, is on the stack, so further method invocations just need to fill method arguments for the next method invocation, which is terminated by build(), which is then returned from the method
    • better understanding by humans, as the scope of mutable state (the builder) is kept to a minimum and is very localized
    • better optimization opportunities, as the object scope is minimized in terms of invocation (rather than method) stack, making escape analysis a lot easier. Given enough compiler (JIT/AOT) prowess, the cost of th builder object can be completely eliminated
    See Also:
    Server, Builder

    • Constructor Detail

      • ServerBuilder

        public ServerBuilder()

      • ServerBuilder

        public ServerBuilder​(Server base)

    • Method Detail

      • getBindingAddress

        public org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.ietf.inet.types.rev130715.IpAddressNoZone getBindingAddress()

      • getBindingPort

        public org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.ietf.inet.types.rev130715.PortNumber getBindingPort()

      • augmentation

        public <E$$ extends org.opendaylight.yangtools.yang.binding.Augmentation<Server>> E$$ augmentation​(Class<E$$> augmentationType)

      • setBindingAddress

        public ServerBuilder setBindingAddress​(org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.ietf.inet.types.rev130715.IpAddressNoZone value)

      • setBindingPort

        public ServerBuilder setBindingPort​(org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.ietf.inet.types.rev130715.PortNumber value)

      • addAugmentation

        public ServerBuilder addAugmentation​(org.opendaylight.yangtools.yang.binding.Augmentation<Server> augmentation)
        Add an augmentation to this builder's product.
        Parameters:
        augmentation - augmentation to be added
        Returns:
        this builder
        Throws:
        NullPointerException - if augmentation is null

      • removeAugmentation

        public ServerBuilder removeAugmentation​(Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<Server>> augmentationType)
        Remove an augmentation from this builder's product. If this builder does not track such an augmentation type, this method does nothing.
        Parameters:
        augmentationType - augmentation type to be removed
        Returns:
        this builder

      • build

        public Server build()
        Specified by:
        build in interface org.opendaylight.yangtools.concepts.Builder<Server>
        Specified by:
        build in interface org.opendaylight.yangtools.concepts.CheckedBuilder<Server,​IllegalArgumentException>