Class NxmNxNspBuilder

  • All Implemented Interfaces:
    org.opendaylight.yangtools.concepts.Builder<NxmNxNsp>, org.opendaylight.yangtools.concepts.CheckedBuilder<NxmNxNsp,​IllegalArgumentException>, org.opendaylight.yangtools.concepts.Mutable, org.opendaylight.yangtools.concepts.MutationBehaviour<org.opendaylight.yangtools.concepts.Mutable>

    @Generated("mdsal-binding-generator")
    public class NxmNxNspBuilder
    extends Object
    implements org.opendaylight.yangtools.concepts.Builder<NxmNxNsp>
    Class that builds NxmNxNspBuilder 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:

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

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

      • NxmNxNspBuilder

        public NxmNxNspBuilder()
      • NxmNxNspBuilder

        public NxmNxNspBuilder​(NxmNxNsp base)
    • Method Detail

      • getValue

        public org.opendaylight.yangtools.yang.common.Uint32 getValue()
      • augmentation

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

        public NxmNxNspBuilder setValue​(org.opendaylight.yangtools.yang.common.Uint32 value)
      • setValue

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

        public NxmNxNspBuilder addAugmentation​(org.opendaylight.yangtools.yang.binding.Augmentation<NxmNxNsp> 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 NxmNxNspBuilder removeAugmentation​(Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<NxmNxNsp>> 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
      • build

        public NxmNxNsp build()
        Specified by:
        build in interface org.opendaylight.yangtools.concepts.Builder<NxmNxNsp>
        Specified by:
        build in interface org.opendaylight.yangtools.concepts.CheckedBuilder<NxmNxNsp,​IllegalArgumentException>