Class DeleteEVPNInputBuilder

  • All Implemented Interfaces:
    org.opendaylight.yangtools.concepts.Builder<DeleteEVPNInput>, org.opendaylight.yangtools.concepts.CheckedBuilder<DeleteEVPNInput,​java.lang.IllegalArgumentException>, org.opendaylight.yangtools.concepts.Mutable, org.opendaylight.yangtools.concepts.MutationBehaviour<org.opendaylight.yangtools.concepts.Mutable>

    public class DeleteEVPNInputBuilder
    extends java.lang.Object
    implements org.opendaylight.yangtools.concepts.Builder<DeleteEVPNInput>
    Class that builds DeleteEVPNInputBuilder 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:

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

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

      • DeleteEVPNInputBuilder

        public DeleteEVPNInputBuilder()
      • DeleteEVPNInputBuilder

        public DeleteEVPNInputBuilder​(DeleteEVPNInput base)
    • Method Detail

      • getId

        public java.util.List<org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.ietf.yang.types.rev130715.Uuid> getId()
      • augmentation

        public <E$$ extends org.opendaylight.yangtools.yang.binding.Augmentation<DeleteEVPNInput>> E$$ augmentation​(java.lang.Class<E$$> augmentationType)
      • setId

        public DeleteEVPNInputBuilder setId​(java.util.List<org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.ietf.yang.types.rev130715.Uuid> values)
      • addAugmentation

        public DeleteEVPNInputBuilder addAugmentation​(java.lang.Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<DeleteEVPNInput>> augmentationType,
                                                      org.opendaylight.yangtools.yang.binding.Augmentation<DeleteEVPNInput> augmentationValue)
      • removeAugmentation

        public DeleteEVPNInputBuilder removeAugmentation​(java.lang.Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<DeleteEVPNInput>> augmentationType)
      • build

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