Package org.opendaylight.yang.gen.v1.urn.opendaylight.flow.inventory.rev130819.flow.node

Class SwitchFeaturesBuilder

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

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

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

    • Constructor Detail

      • SwitchFeaturesBuilder

        public SwitchFeaturesBuilder()

      • SwitchFeaturesBuilder

        public SwitchFeaturesBuilder​(SwitchFeatures base)

    • Method Detail

      • getMaxBuffers

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

      • getMaxTables

        public org.opendaylight.yangtools.yang.common.Uint8 getMaxTables()

      • augmentation

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

      • setMaxBuffers

        public SwitchFeaturesBuilder setMaxBuffers​(org.opendaylight.yangtools.yang.common.Uint32 value)

      • setMaxBuffers

        @Deprecated(forRemoval=true)
public SwitchFeaturesBuilder setMaxBuffers​(Long value)
        Deprecated, for removal: This API element is subject to removal in a future version.
        Use {#link setMaxBuffers(Uint32)} instead.
        Utility migration setter.
        Parameters:
        value - field value in legacy type
        Returns:
        this builder

      • setMaxTables

        public SwitchFeaturesBuilder setMaxTables​(org.opendaylight.yangtools.yang.common.Uint8 value)

      • setMaxTables

        @Deprecated(forRemoval=true)
public SwitchFeaturesBuilder setMaxTables​(Short value)
        Deprecated, for removal: This API element is subject to removal in a future version.
        Use {#link setMaxTables(Uint8)} instead.
        Utility migration setter.
        Parameters:
        value - field value in legacy type
        Returns:
        this builder