Class RpcRouteBuilder
- java.lang.Object
-
- org.opendaylight.yang.gen.v1.rpcbench.payload.rev150702.rpcbench.rpc.routes.RpcRouteBuilder
-
- All Implemented Interfaces:
org.opendaylight.yangtools.concepts.Builder<RpcRoute>,org.opendaylight.yangtools.concepts.CheckedBuilder<RpcRoute,IllegalArgumentException>,org.opendaylight.yangtools.concepts.Mutable,org.opendaylight.yangtools.concepts.MutationBehaviour<org.opendaylight.yangtools.concepts.Mutable>
@Generated("mdsal-binding-generator") public class RpcRouteBuilder extends Object implements org.opendaylight.yangtools.concepts.Builder<RpcRoute>
Class that buildsRpcRouteBuilderinstances. 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:
RpcRouteBuilder createTarget(int fooXyzzy, int barBaz) { return new RpcRouteBuilderBuilder() .setFoo(new FooBuilder().setXyzzy(fooXyzzy).build()) .setBar(new BarBuilder().setBaz(barBaz).build()) .build(); }This pattern is supported by the immutable nature of RpcRouteBuilder, 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:
RpcRouteBuilder,Builder
-
-
Constructor Summary
Constructors Constructor Description RpcRouteBuilder()RpcRouteBuilder(RpcRoute base)
-
Method Summary
All Methods Instance Methods Concrete Methods Modifier and Type Method Description RpcRouteBuilderaddAugmentation(org.opendaylight.yangtools.yang.binding.Augmentation<RpcRoute> augmentation)Add an augmentation to this builder's product.<E$$ extends org.opendaylight.yangtools.yang.binding.Augmentation<RpcRoute>>
E$$augmentation(Class<E$$> augmentationType)RpcRoutebuild()StringgetId()RpcRouteKeykey()RpcRouteBuilderremoveAugmentation(Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<RpcRoute>> augmentationType)Remove an augmentation from this builder's product.RpcRouteBuildersetId(String value)RpcRouteBuilderwithKey(RpcRouteKey key)
-
-
-
Constructor Detail
-
RpcRouteBuilder
public RpcRouteBuilder()
-
RpcRouteBuilder
public RpcRouteBuilder(RpcRoute base)
-
-
Method Detail
-
key
public RpcRouteKey key()
-
getId
public String getId()
-
augmentation
public <E$$ extends org.opendaylight.yangtools.yang.binding.Augmentation<RpcRoute>> E$$ augmentation(Class<E$$> augmentationType)
-
withKey
public RpcRouteBuilder withKey(RpcRouteKey key)
-
setId
public RpcRouteBuilder setId(String value)
-
addAugmentation
public RpcRouteBuilder addAugmentation(org.opendaylight.yangtools.yang.binding.Augmentation<RpcRoute> augmentation)
Add an augmentation to this builder's product.- Parameters:
augmentation- augmentation to be added- Returns:
- this builder
- Throws:
NullPointerException- ifaugmentationis null
-
removeAugmentation
public RpcRouteBuilder removeAugmentation(Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<RpcRoute>> 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 RpcRoute build()
- Specified by:
buildin interfaceorg.opendaylight.yangtools.concepts.Builder<RpcRoute>- Specified by:
buildin interfaceorg.opendaylight.yangtools.concepts.CheckedBuilder<RpcRoute,IllegalArgumentException>
-
-