Package org.opendaylight.yang.gen.v1.http.openconfig.net.yang.system.logging.rev181121.logging.top

Class LoggingBuilder

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

       
     Logging createLogging(int fooXyzzy, int barBaz) {
         return new LoggingBuilder()
             .setFoo(new FooBuilder().setXyzzy(fooXyzzy).build())
             .setBar(new BarBuilder().setBaz(barBaz).build())
             .build();
     }

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

    • Constructor Detail

      • LoggingBuilder

        public LoggingBuilder()

      • LoggingBuilder

        public LoggingBuilder​(Logging base)

    • Method Detail

      • fieldsFrom

        public void fieldsFrom​(org.opendaylight.yangtools.yang.binding.DataObject arg)
        Set fields from given grouping argument. Valid argument is instance of one of following types:
        • LoggingConsoleTop
        • LoggingRemoteTop
        Parameters:
        arg - grouping object
        Throws:
        IllegalArgumentException - if given argument is none of valid types or has property with incompatible value

      • getConsole

        public Console getConsole()

      • augmentation

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

      • addAugmentation

        public LoggingBuilder addAugmentation​(org.opendaylight.yangtools.yang.binding.Augmentation<Logging> 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 LoggingBuilder removeAugmentation​(Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<Logging>> 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 Logging build()
        Specified by:
        build in interface org.opendaylight.yangtools.concepts.Builder<Logging>
        Specified by:
        build in interface org.opendaylight.yangtools.concepts.CheckedBuilder<Logging,​IllegalArgumentException>