Class NxActionDecapRpcRemoveFlowWriteActionsCaseBuilder
- java.lang.Object
-
- org.opendaylight.yang.gen.v1.urn.opendaylight.openflowplugin.extension.nicira.action.rev140714.remove.flow.input.instructions.instruction.instruction.write.actions._case.write.actions.action.action.NxActionDecapRpcRemoveFlowWriteActionsCaseBuilder
-
- All Implemented Interfaces:
org.opendaylight.yangtools.concepts.Builder<NxActionDecapRpcRemoveFlowWriteActionsCase>
,org.opendaylight.yangtools.concepts.CheckedBuilder<NxActionDecapRpcRemoveFlowWriteActionsCase,IllegalArgumentException>
,org.opendaylight.yangtools.concepts.Mutable
,org.opendaylight.yangtools.concepts.MutationBehaviour<org.opendaylight.yangtools.concepts.Mutable>
public class NxActionDecapRpcRemoveFlowWriteActionsCaseBuilder extends Object implements org.opendaylight.yangtools.concepts.Builder<NxActionDecapRpcRemoveFlowWriteActionsCase>
Class that buildsNxActionDecapRpcRemoveFlowWriteActionsCaseBuilder
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:
NxActionDecapRpcRemoveFlowWriteActionsCaseBuilder createTarget(int fooXyzzy, int barBaz) { return new NxActionDecapRpcRemoveFlowWriteActionsCaseBuilderBuilder() .setFoo(new FooBuilder().setXyzzy(fooXyzzy).build()) .setBar(new BarBuilder().setBaz(barBaz).build()) .build(); }
This pattern is supported by the immutable nature of NxActionDecapRpcRemoveFlowWriteActionsCaseBuilder, 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:
NxActionDecapRpcRemoveFlowWriteActionsCaseBuilder
,Builder
-
-
Constructor Summary
Constructors Constructor Description NxActionDecapRpcRemoveFlowWriteActionsCaseBuilder()
NxActionDecapRpcRemoveFlowWriteActionsCaseBuilder(NxActionDecapGrouping arg)
NxActionDecapRpcRemoveFlowWriteActionsCaseBuilder(NxActionDecapRpcRemoveFlowWriteActionsCase base)
-
Method Summary
All Methods Instance Methods Concrete Methods Modifier and Type Method Description NxActionDecapRpcRemoveFlowWriteActionsCaseBuilder
addAugmentation(Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<NxActionDecapRpcRemoveFlowWriteActionsCase>> augmentationType, org.opendaylight.yangtools.yang.binding.Augmentation<NxActionDecapRpcRemoveFlowWriteActionsCase> augmentationValue)
<E$$ extends org.opendaylight.yangtools.yang.binding.Augmentation<NxActionDecapRpcRemoveFlowWriteActionsCase>>
E$$augmentation(Class<E$$> augmentationType)
NxActionDecapRpcRemoveFlowWriteActionsCase
build()
void
fieldsFrom(org.opendaylight.yangtools.yang.binding.DataObject arg)
Set fields from given grouping argument.NxDecap
getNxDecap()
NxActionDecapRpcRemoveFlowWriteActionsCaseBuilder
removeAugmentation(Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<NxActionDecapRpcRemoveFlowWriteActionsCase>> augmentationType)
NxActionDecapRpcRemoveFlowWriteActionsCaseBuilder
setNxDecap(NxDecap value)
-
-
-
Constructor Detail
-
NxActionDecapRpcRemoveFlowWriteActionsCaseBuilder
public NxActionDecapRpcRemoveFlowWriteActionsCaseBuilder()
-
NxActionDecapRpcRemoveFlowWriteActionsCaseBuilder
public NxActionDecapRpcRemoveFlowWriteActionsCaseBuilder(NxActionDecapGrouping arg)
-
NxActionDecapRpcRemoveFlowWriteActionsCaseBuilder
public NxActionDecapRpcRemoveFlowWriteActionsCaseBuilder(NxActionDecapRpcRemoveFlowWriteActionsCase 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.NxActionDecapGrouping
- Parameters:
arg
- grouping object- Throws:
IllegalArgumentException
- if given argument is none of valid types
-
getNxDecap
public NxDecap getNxDecap()
-
augmentation
public <E$$ extends org.opendaylight.yangtools.yang.binding.Augmentation<NxActionDecapRpcRemoveFlowWriteActionsCase>> E$$ augmentation(Class<E$$> augmentationType)
-
setNxDecap
public NxActionDecapRpcRemoveFlowWriteActionsCaseBuilder setNxDecap(NxDecap value)
-
addAugmentation
public NxActionDecapRpcRemoveFlowWriteActionsCaseBuilder addAugmentation(Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<NxActionDecapRpcRemoveFlowWriteActionsCase>> augmentationType, org.opendaylight.yangtools.yang.binding.Augmentation<NxActionDecapRpcRemoveFlowWriteActionsCase> augmentationValue)
-
removeAugmentation
public NxActionDecapRpcRemoveFlowWriteActionsCaseBuilder removeAugmentation(Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<NxActionDecapRpcRemoveFlowWriteActionsCase>> augmentationType)
-
build
public NxActionDecapRpcRemoveFlowWriteActionsCase build()
- Specified by:
build
in interfaceorg.opendaylight.yangtools.concepts.Builder<NxActionDecapRpcRemoveFlowWriteActionsCase>
- Specified by:
build
in interfaceorg.opendaylight.yangtools.concepts.CheckedBuilder<NxActionDecapRpcRemoveFlowWriteActionsCase,IllegalArgumentException>
-
-