Class MultipartRequestQueueBuilder

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

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

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

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

      • MultipartRequestQueueBuilder

        public MultipartRequestQueueBuilder()
    • Method Detail

      • getPortNo

        public org.opendaylight.yangtools.yang.common.Uint32 getPortNo()
      • getQueueId

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

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

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