Class NxActionCtClearRpcAddFlowWriteActionsCaseBuilder
- java.lang.Object
-
- org.opendaylight.yang.gen.v1.urn.opendaylight.openflowplugin.extension.nicira.action.rev140714.add.flow.input.instructions.instruction.instruction.write.actions._case.write.actions.action.action.NxActionCtClearRpcAddFlowWriteActionsCaseBuilder
-
- All Implemented Interfaces:
org.opendaylight.yangtools.concepts.Builder<NxActionCtClearRpcAddFlowWriteActionsCase>
,org.opendaylight.yangtools.concepts.CheckedBuilder<NxActionCtClearRpcAddFlowWriteActionsCase,IllegalArgumentException>
,org.opendaylight.yangtools.concepts.Mutable
,org.opendaylight.yangtools.concepts.MutationBehaviour<org.opendaylight.yangtools.concepts.Mutable>
@Generated("mdsal-binding-generator") public class NxActionCtClearRpcAddFlowWriteActionsCaseBuilder extends Object implements org.opendaylight.yangtools.concepts.Builder<NxActionCtClearRpcAddFlowWriteActionsCase>
Class that buildsNxActionCtClearRpcAddFlowWriteActionsCaseBuilder
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:
NxActionCtClearRpcAddFlowWriteActionsCaseBuilder createTarget(int fooXyzzy, int barBaz) { return new NxActionCtClearRpcAddFlowWriteActionsCaseBuilderBuilder() .setFoo(new FooBuilder().setXyzzy(fooXyzzy).build()) .setBar(new BarBuilder().setBaz(barBaz).build()) .build(); }
This pattern is supported by the immutable nature of NxActionCtClearRpcAddFlowWriteActionsCaseBuilder, 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:
NxActionCtClearRpcAddFlowWriteActionsCaseBuilder
,Builder
-
-
Constructor Summary
Constructors Constructor Description NxActionCtClearRpcAddFlowWriteActionsCaseBuilder()
NxActionCtClearRpcAddFlowWriteActionsCaseBuilder(NxActionCtClearRpcAddFlowWriteActionsCase base)
NxActionCtClearRpcAddFlowWriteActionsCaseBuilder(NxActionCtClearGrouping arg)
-
Method Summary
All Methods Instance Methods Concrete Methods Modifier and Type Method Description NxActionCtClearRpcAddFlowWriteActionsCaseBuilder
addAugmentation(org.opendaylight.yangtools.yang.binding.Augmentation<NxActionCtClearRpcAddFlowWriteActionsCase> augmentation)
Add an augmentation to this builder's product.<E$$ extends org.opendaylight.yangtools.yang.binding.Augmentation<NxActionCtClearRpcAddFlowWriteActionsCase>>
E$$augmentation(Class<E$$> augmentationType)
NxActionCtClearRpcAddFlowWriteActionsCase
build()
void
fieldsFrom(org.opendaylight.yangtools.yang.binding.DataObject arg)
Set fields from given grouping argument.NxCtClear
getNxCtClear()
NxActionCtClearRpcAddFlowWriteActionsCaseBuilder
removeAugmentation(Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<NxActionCtClearRpcAddFlowWriteActionsCase>> augmentationType)
Remove an augmentation from this builder's product.NxActionCtClearRpcAddFlowWriteActionsCaseBuilder
setNxCtClear(NxCtClear value)
-
-
-
Constructor Detail
-
NxActionCtClearRpcAddFlowWriteActionsCaseBuilder
public NxActionCtClearRpcAddFlowWriteActionsCaseBuilder()
-
NxActionCtClearRpcAddFlowWriteActionsCaseBuilder
public NxActionCtClearRpcAddFlowWriteActionsCaseBuilder(NxActionCtClearGrouping arg)
-
NxActionCtClearRpcAddFlowWriteActionsCaseBuilder
public NxActionCtClearRpcAddFlowWriteActionsCaseBuilder(NxActionCtClearRpcAddFlowWriteActionsCase 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:- org.opendaylight.yang.gen.v1.urn.opendaylight.openflowplugin.extension.nicira.action.rev140714.NxActionCtClearGrouping
- Parameters:
arg
- grouping object- Throws:
IllegalArgumentException
- if given argument is none of valid types or has property with incompatible value
-
getNxCtClear
public NxCtClear getNxCtClear()
-
augmentation
public <E$$ extends org.opendaylight.yangtools.yang.binding.Augmentation<NxActionCtClearRpcAddFlowWriteActionsCase>> E$$ augmentation(Class<E$$> augmentationType)
-
setNxCtClear
public NxActionCtClearRpcAddFlowWriteActionsCaseBuilder setNxCtClear(NxCtClear value)
-
addAugmentation
public NxActionCtClearRpcAddFlowWriteActionsCaseBuilder addAugmentation(org.opendaylight.yangtools.yang.binding.Augmentation<NxActionCtClearRpcAddFlowWriteActionsCase> augmentation)
Add an augmentation to this builder's product.- Parameters:
augmentation
- augmentation to be added- Returns:
- this builder
- Throws:
NullPointerException
- ifaugmentation
is null
-
removeAugmentation
public NxActionCtClearRpcAddFlowWriteActionsCaseBuilder removeAugmentation(Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<NxActionCtClearRpcAddFlowWriteActionsCase>> 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 NxActionCtClearRpcAddFlowWriteActionsCase build()
- Specified by:
build
in interfaceorg.opendaylight.yangtools.concepts.Builder<NxActionCtClearRpcAddFlowWriteActionsCase>
- Specified by:
build
in interfaceorg.opendaylight.yangtools.concepts.CheckedBuilder<NxActionCtClearRpcAddFlowWriteActionsCase,IllegalArgumentException>
-
-