Package org.opendaylight.yang.gen.v1.urn.opendaylight.lfm.mappingservice.rev150906

Class MappingChangedBuilder

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

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

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

    • Constructor Detail

      • MappingChangedBuilder

        public MappingChangedBuilder()

      • MappingChangedBuilder

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

      • MappingChangedBuilder

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

      • MappingChangedBuilder

        public MappingChangedBuilder​(MappingChanged 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.EidContainer
        • org.opendaylight.yang.gen.v1.urn.opendaylight.lfm.lisp.proto.rev151105.MappingRecordContainer
        Parameters:
        arg - grouping object
        Throws:
        IllegalArgumentException - if given argument is none of valid types

      • getEid

        public org.opendaylight.yang.gen.v1.urn.opendaylight.lfm.lisp.proto.rev151105.eid.container.Eid getEid()

      • getMappingRecord

        public org.opendaylight.yang.gen.v1.urn.opendaylight.lfm.lisp.proto.rev151105.mapping.record.container.MappingRecord getMappingRecord()

      • augmentation

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

      • setEid

        public MappingChangedBuilder setEid​(org.opendaylight.yang.gen.v1.urn.opendaylight.lfm.lisp.proto.rev151105.eid.container.Eid value)

      • setMappingRecord

        public MappingChangedBuilder setMappingRecord​(org.opendaylight.yang.gen.v1.urn.opendaylight.lfm.lisp.proto.rev151105.mapping.record.container.MappingRecord value)