Package org.opendaylight.yang.gen.v1.urn.opendaylight.openflowjava.nx.match.rev140421.ofj.nxm.nx.match.ct.state.grouping

Class CtStateValuesBuilder

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

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

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

    • Constructor Detail

      • CtStateValuesBuilder

        public CtStateValuesBuilder()

      • CtStateValuesBuilder

        public CtStateValuesBuilder​(CtStateValues base)

    • Method Detail

      • getCtState

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

      • getMask

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

      • augmentation

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

      • setCtState

        public CtStateValuesBuilder setCtState​(org.opendaylight.yangtools.yang.common.Uint32 value)

      • setMask

        public CtStateValuesBuilder setMask​(org.opendaylight.yangtools.yang.common.Uint32 value)

      • setMask

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

      • addAugmentation

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