Class State4Builder
- java.lang.Object
-
- org.opendaylight.yang.gen.v1.http.openconfig.net.yang.bgp.rev151009.State4Builder
-
- All Implemented Interfaces:
org.opendaylight.yangtools.concepts.Builder<State4>
,org.opendaylight.yangtools.concepts.CheckedBuilder<State4,IllegalArgumentException>
,org.opendaylight.yangtools.concepts.Mutable
,org.opendaylight.yangtools.concepts.MutationBehaviour<org.opendaylight.yangtools.concepts.Mutable>
public class State4Builder extends Object implements org.opendaylight.yangtools.concepts.Builder<State4>
Class that buildsState4Builder
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:
State4Builder createTarget(int fooXyzzy, int barBaz) { return new State4BuilderBuilder() .setFoo(new FooBuilder().setXyzzy(fooXyzzy).build()) .setBar(new BarBuilder().setBaz(barBaz).build()) .build(); }
This pattern is supported by the immutable nature of State4Builder, 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:
State4Builder
,Builder
-
-
Constructor Summary
Constructors Constructor Description State4Builder()
State4Builder(BgpNeighborErrorHandlingState arg)
State4Builder(State4 base)
-
Method Summary
All Methods Instance Methods Concrete Methods Deprecated Methods Modifier and Type Method Description State4
build()
void
fieldsFrom(org.opendaylight.yangtools.yang.binding.DataObject arg)
Set fields from given grouping argument.org.opendaylight.yangtools.yang.common.Uint32
getErroneousUpdateMessages()
State4Builder
setErroneousUpdateMessages(Long value)
Deprecated, for removal: This API element is subject to removal in a future version.Use {#link setErroneousUpdateMessages(Uint32)} instead.State4Builder
setErroneousUpdateMessages(org.opendaylight.yangtools.yang.common.Uint32 value)
-
-
-
Constructor Detail
-
State4Builder
public State4Builder()
-
State4Builder
public State4Builder(BgpNeighborErrorHandlingState arg)
-
State4Builder
public State4Builder(State4 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.http.openconfig.net.yang.bgp.operational.rev151009.BgpNeighborErrorHandlingState
- Parameters:
arg
- grouping object- Throws:
IllegalArgumentException
- if given argument is none of valid types
-
getErroneousUpdateMessages
public org.opendaylight.yangtools.yang.common.Uint32 getErroneousUpdateMessages()
-
setErroneousUpdateMessages
public State4Builder setErroneousUpdateMessages(org.opendaylight.yangtools.yang.common.Uint32 value)
-
setErroneousUpdateMessages
@Deprecated(forRemoval=true) public State4Builder setErroneousUpdateMessages(Long value)
Deprecated, for removal: This API element is subject to removal in a future version.Use {#link setErroneousUpdateMessages(Uint32)} instead.Utility migration setter.- Parameters:
value
- field value in legacy type- Returns:
- this builder
-
build
public State4 build()
- Specified by:
build
in interfaceorg.opendaylight.yangtools.concepts.Builder<State4>
- Specified by:
build
in interfaceorg.opendaylight.yangtools.concepts.CheckedBuilder<State4,IllegalArgumentException>
-
-