Package org.opendaylight.yang.gen.v1.urn.opendaylight.lfm.lisp.sb.rev150904

Class SendMapReplyInputBuilder

  • All Implemented Interfaces:
    org.opendaylight.yangtools.concepts.Builder<SendMapReplyInput>, org.opendaylight.yangtools.concepts.CheckedBuilder<SendMapReplyInput,​IllegalArgumentException>, org.opendaylight.yangtools.concepts.Mutable, org.opendaylight.yangtools.concepts.MutationBehaviour<org.opendaylight.yangtools.concepts.Mutable>
    public class SendMapReplyInputBuilder
extends Object
implements org.opendaylight.yangtools.concepts.Builder<SendMapReplyInput>
    Class that builds SendMapReplyInputBuilder 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: 

       
     SendMapReplyInputBuilder createTarget(int fooXyzzy, int barBaz) {
         return new SendMapReplyInputBuilderBuilder()
             .setFoo(new FooBuilder().setXyzzy(fooXyzzy).build())
             .setBar(new BarBuilder().setBaz(barBaz).build())
             .build();
     }

    This pattern is supported by the immutable nature of SendMapReplyInputBuilder, 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 oportunities, 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:
    SendMapReplyInputBuilder, Builder

    • Constructor Detail

      • SendMapReplyInputBuilder

        public SendMapReplyInputBuilder()

      • SendMapReplyInputBuilder

        public SendMapReplyInputBuilder​(org.opendaylight.yang.gen.v1.urn.opendaylight.lfm.lisp.proto.rev151105.MapReplyMessage arg)

      • SendMapReplyInputBuilder

        public SendMapReplyInputBuilder​(org.opendaylight.yang.gen.v1.urn.opendaylight.lfm.lisp.proto.rev151105.TransportAddress arg)

      • SendMapReplyInputBuilder

        public SendMapReplyInputBuilder​(SendMapReplyInput base)

    • Method Detail

      • fieldsFrom

        public void fieldsFrom​(org.opendaylight.yangtools.yang.binding.DataObject arg)
        Set fields from given grouping argument. Valid argument is instance of one of following types:
        • org.opendaylight.yang.gen.v1.urn.opendaylight.lfm.lisp.proto.rev151105.MapReplyMessage
        • org.opendaylight.yang.gen.v1.urn.opendaylight.lfm.lisp.proto.rev151105.TransportAddress
        Parameters:
        arg - grouping object
        Throws:
        IllegalArgumentException - if given argument is none of valid types

      • getMapReply

        public org.opendaylight.yang.gen.v1.urn.opendaylight.lfm.lisp.proto.rev151105.mapreplymessage.MapReply getMapReply()

      • getTransportAddress

        public org.opendaylight.yang.gen.v1.urn.opendaylight.lfm.lisp.proto.rev151105.transport.address.TransportAddress getTransportAddress()

      • augmentation

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

      • setMapReply

        public SendMapReplyInputBuilder setMapReply​(org.opendaylight.yang.gen.v1.urn.opendaylight.lfm.lisp.proto.rev151105.mapreplymessage.MapReply value)

      • setTransportAddress

        public SendMapReplyInputBuilder setTransportAddress​(org.opendaylight.yang.gen.v1.urn.opendaylight.lfm.lisp.proto.rev151105.transport.address.TransportAddress value)