Class NxActionEncapRpcRemoveFlowWriteActionsCaseBuilder
- 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.NxActionEncapRpcRemoveFlowWriteActionsCaseBuilder
-
- All Implemented Interfaces:
org.opendaylight.yangtools.concepts.Builder<NxActionEncapRpcRemoveFlowWriteActionsCase>
,org.opendaylight.yangtools.concepts.CheckedBuilder<NxActionEncapRpcRemoveFlowWriteActionsCase,IllegalArgumentException>
,org.opendaylight.yangtools.concepts.Mutable
,org.opendaylight.yangtools.concepts.MutationBehaviour<org.opendaylight.yangtools.concepts.Mutable>
public class NxActionEncapRpcRemoveFlowWriteActionsCaseBuilder extends Object implements org.opendaylight.yangtools.concepts.Builder<NxActionEncapRpcRemoveFlowWriteActionsCase>
Class that buildsNxActionEncapRpcRemoveFlowWriteActionsCaseBuilder
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:
NxActionEncapRpcRemoveFlowWriteActionsCaseBuilder createTarget(int fooXyzzy, int barBaz) { return new NxActionEncapRpcRemoveFlowWriteActionsCaseBuilderBuilder() .setFoo(new FooBuilder().setXyzzy(fooXyzzy).build()) .setBar(new BarBuilder().setBaz(barBaz).build()) .build(); }
This pattern is supported by the immutable nature of NxActionEncapRpcRemoveFlowWriteActionsCaseBuilder, 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:
NxActionEncapRpcRemoveFlowWriteActionsCaseBuilder
,Builder
-
-
Constructor Summary
Constructors Constructor Description NxActionEncapRpcRemoveFlowWriteActionsCaseBuilder()
NxActionEncapRpcRemoveFlowWriteActionsCaseBuilder(NxActionEncapGrouping arg)
NxActionEncapRpcRemoveFlowWriteActionsCaseBuilder(NxActionEncapRpcRemoveFlowWriteActionsCase base)
-
Method Summary
All Methods Instance Methods Concrete Methods Modifier and Type Method Description NxActionEncapRpcRemoveFlowWriteActionsCaseBuilder
addAugmentation(Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<NxActionEncapRpcRemoveFlowWriteActionsCase>> augmentationType, org.opendaylight.yangtools.yang.binding.Augmentation<NxActionEncapRpcRemoveFlowWriteActionsCase> augmentationValue)
<E$$ extends org.opendaylight.yangtools.yang.binding.Augmentation<NxActionEncapRpcRemoveFlowWriteActionsCase>>
E$$augmentation(Class<E$$> augmentationType)
NxActionEncapRpcRemoveFlowWriteActionsCase
build()
void
fieldsFrom(org.opendaylight.yangtools.yang.binding.DataObject arg)
Set fields from given grouping argument.NxEncap
getNxEncap()
NxActionEncapRpcRemoveFlowWriteActionsCaseBuilder
removeAugmentation(Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<NxActionEncapRpcRemoveFlowWriteActionsCase>> augmentationType)
NxActionEncapRpcRemoveFlowWriteActionsCaseBuilder
setNxEncap(NxEncap value)
-
-
-
Constructor Detail
-
NxActionEncapRpcRemoveFlowWriteActionsCaseBuilder
public NxActionEncapRpcRemoveFlowWriteActionsCaseBuilder()
-
NxActionEncapRpcRemoveFlowWriteActionsCaseBuilder
public NxActionEncapRpcRemoveFlowWriteActionsCaseBuilder(NxActionEncapGrouping arg)
-
NxActionEncapRpcRemoveFlowWriteActionsCaseBuilder
public NxActionEncapRpcRemoveFlowWriteActionsCaseBuilder(NxActionEncapRpcRemoveFlowWriteActionsCase 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.NxActionEncapGrouping
- Parameters:
arg
- grouping object- Throws:
IllegalArgumentException
- if given argument is none of valid types
-
getNxEncap
public NxEncap getNxEncap()
-
augmentation
public <E$$ extends org.opendaylight.yangtools.yang.binding.Augmentation<NxActionEncapRpcRemoveFlowWriteActionsCase>> E$$ augmentation(Class<E$$> augmentationType)
-
setNxEncap
public NxActionEncapRpcRemoveFlowWriteActionsCaseBuilder setNxEncap(NxEncap value)
-
addAugmentation
public NxActionEncapRpcRemoveFlowWriteActionsCaseBuilder addAugmentation(Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<NxActionEncapRpcRemoveFlowWriteActionsCase>> augmentationType, org.opendaylight.yangtools.yang.binding.Augmentation<NxActionEncapRpcRemoveFlowWriteActionsCase> augmentationValue)
-
removeAugmentation
public NxActionEncapRpcRemoveFlowWriteActionsCaseBuilder removeAugmentation(Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<NxActionEncapRpcRemoveFlowWriteActionsCase>> augmentationType)
-
build
public NxActionEncapRpcRemoveFlowWriteActionsCase build()
- Specified by:
build
in interfaceorg.opendaylight.yangtools.concepts.Builder<NxActionEncapRpcRemoveFlowWriteActionsCase>
- Specified by:
build
in interfaceorg.opendaylight.yangtools.concepts.CheckedBuilder<NxActionEncapRpcRemoveFlowWriteActionsCase,IllegalArgumentException>
-
-