org.opendaylight.yang.gen.v1.urn.opendaylight.openflowplugin.extension.nicira.action.rev140714.nx.action.ct.clear.grouping

Class NxCtClearBuilder

java.lang.Object

org.opendaylight.yang.gen.v1.urn.opendaylight.openflowplugin.extension.nicira.action.rev140714.nx.action.ct.clear.grouping.NxCtClearBuilder

All Implemented Interfaces:

org.opendaylight.yangtools.concepts.Builder<NxCtClear>, org.opendaylight.yangtools.concepts.CheckedBuilder<NxCtClear,IllegalArgumentException>, org.opendaylight.yangtools.concepts.Mutable, org.opendaylight.yangtools.concepts.MutationBehaviour<org.opendaylight.yangtools.concepts.Mutable>

public class NxCtClearBuilder
extends Object
implements org.opendaylight.yangtools.concepts.Builder<NxCtClear>

Class that builds NxCtClearBuilder 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:

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

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

NxCtClearBuilder, Builder

Constructor Summary

Constructors

Constructor and Description
NxCtClearBuilder()
NxCtClearBuilder(NxCtClear base)

Method Summary

Modifier and Type	Method and Description
NxCtClearBuilder	addAugmentation(Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<NxCtClear>> augmentationType, org.opendaylight.yangtools.yang.binding.Augmentation<NxCtClear> augmentationValue)
<E$$ extends org.opendaylight.yangtools.yang.binding.Augmentation<NxCtClear>> E$$	augmentation(Class<E$$> augmentationType)
NxCtClear	build()
NxCtClearBuilder	removeAugmentation(Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<NxCtClear>> augmentationType)

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

NxCtClearBuilder

public NxCtClearBuilder()

NxCtClearBuilder

public NxCtClearBuilder(NxCtClear base)

Method Detail

augmentation

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

addAugmentation

public NxCtClearBuilder addAugmentation(Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<NxCtClear>> augmentationType,
                                        org.opendaylight.yangtools.yang.binding.Augmentation<NxCtClear> augmentationValue)

removeAugmentation

public NxCtClearBuilder removeAugmentation(Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<NxCtClear>> augmentationType)

build

public NxCtClear build()

Specified by:

build in interface org.opendaylight.yangtools.concepts.CheckedBuilder<NxCtClear,IllegalArgumentException>