Package org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.pcep.segment.routing.rev200720.sr.subobject.nai

Class UnnumberedAdjacencyBuilder

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

       
     UnnumberedAdjacency createUnnumberedAdjacency(int fooXyzzy, int barBaz) {
         return new UnnumberedAdjacencyBuilder()
             .setFoo(new FooBuilder().setXyzzy(fooXyzzy).build())
             .setBar(new BarBuilder().setBaz(barBaz).build())
             .build();
     }

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

    • Constructor Detail

      • UnnumberedAdjacencyBuilder

        public UnnumberedAdjacencyBuilder()

    • Method Detail

      • getLocalInterfaceId

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

      • getLocalNodeId

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

      • getRemoteInterfaceId

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

      • getRemoteNodeId

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

      • augmentation

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

      • setLocalInterfaceId

        public UnnumberedAdjacencyBuilder setLocalInterfaceId​(org.opendaylight.yangtools.yang.common.Uint32 value)

      • setRemoteInterfaceId

        public UnnumberedAdjacencyBuilder setRemoteInterfaceId​(org.opendaylight.yangtools.yang.common.Uint32 value)

      • addAugmentation

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