Package org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.topology.tunnel.rev130819

Class Topology1Builder

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

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

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

    • Constructor Detail

      • Topology1Builder

        public Topology1Builder()

      • Topology1Builder

        public Topology1Builder​(Topology1 base)

    • Method Detail

      • setPaths

        @Deprecated(forRemoval=true)
public Topology1Builder setPaths​(List<Paths> values)
        Deprecated, for removal: This API element is subject to removal in a future version.
        Use setPaths(Map) instead.
        Utility migration setter. IMPORTANT NOTE: This method does not completely match previous mechanics, as the list is processed as during this method's execution. Any future modifications of the list are NOT reflected in this builder nor its products.
        Parameters:
        values - Legacy List of values
        Returns:
        this builder
        Throws:
        IllegalArgumentException - if the list contains entries with the same key
        NullPointerException - if the list contains a null entry