Package org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.bgp.segment.routing.ext.rev200120.binding.sub.tlvs.binding.sub.tlv.unnumbered._interface.id.ero._case

Class UnnumberedInterfaceIdEroBuilder

  • All Implemented Interfaces:
    org.opendaylight.yangtools.concepts.Builder<UnnumberedInterfaceIdEro>, org.opendaylight.yangtools.concepts.CheckedBuilder<UnnumberedInterfaceIdEro,​IllegalArgumentException>, org.opendaylight.yangtools.concepts.Mutable, org.opendaylight.yangtools.concepts.MutationBehaviour<org.opendaylight.yangtools.concepts.Mutable>
    @Generated("mdsal-binding-generator")
public class UnnumberedInterfaceIdEroBuilder
extends Object
implements org.opendaylight.yangtools.concepts.Builder<UnnumberedInterfaceIdEro>
    Class that builds UnnumberedInterfaceIdEro 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: 

       
     UnnumberedInterfaceIdEro createUnnumberedInterfaceIdEro(int fooXyzzy, int barBaz) {
         return new UnnumberedInterfaceIdEroBuilder()
             .setFoo(new FooBuilder().setXyzzy(fooXyzzy).build())
             .setBar(new BarBuilder().setBaz(barBaz).build())
             .build();
     }

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

    • Constructor Detail

      • UnnumberedInterfaceIdEroBuilder

        public UnnumberedInterfaceIdEroBuilder()

      • UnnumberedInterfaceIdEroBuilder

        public UnnumberedInterfaceIdEroBuilder​(EroUnnumbered arg)

      • UnnumberedInterfaceIdEroBuilder

        public UnnumberedInterfaceIdEroBuilder​(EroFlags arg)

    • 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:
        • EroUnnumbered
        • EroFlags
        Parameters:
        arg - grouping object
        Throws:
        IllegalArgumentException - if given argument is none of valid types or has property with incompatible value

      • getInterfaceId

        public org.opendaylight.yangtools.yang.common.Uint32 getInterfaceId()

      • getLoose

        public Boolean getLoose()

      • getRouterId

        public org.opendaylight.yangtools.yang.common.Uint32 getRouterId()

      • augmentation

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

      • removeAugmentation

        public UnnumberedInterfaceIdEroBuilder removeAugmentation​(Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<UnnumberedInterfaceIdEro>> 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