Package org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.bgp.openconfig.extensions.rev180329
Class NetworkInstanceProtocolBuilder
- java.lang.Object
-
- org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.bgp.openconfig.extensions.rev180329.NetworkInstanceProtocolBuilder
-
- All Implemented Interfaces:
org.opendaylight.yangtools.concepts.Builder<NetworkInstanceProtocol>
,org.opendaylight.yangtools.concepts.CheckedBuilder<NetworkInstanceProtocol,IllegalArgumentException>
,org.opendaylight.yangtools.concepts.Mutable
,org.opendaylight.yangtools.concepts.MutationBehaviour<org.opendaylight.yangtools.concepts.Mutable>
@Generated("mdsal-binding-generator") public class NetworkInstanceProtocolBuilder extends Object implements org.opendaylight.yangtools.concepts.Builder<NetworkInstanceProtocol>
Class that buildsNetworkInstanceProtocolBuilder
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:
NetworkInstanceProtocolBuilder createTarget(int fooXyzzy, int barBaz) { return new NetworkInstanceProtocolBuilderBuilder() .setFoo(new FooBuilder().setXyzzy(fooXyzzy).build()) .setBar(new BarBuilder().setBaz(barBaz).build()) .build(); }
This pattern is supported by the immutable nature of NetworkInstanceProtocolBuilder, 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:
NetworkInstanceProtocolBuilder
,Builder
-
-
Constructor Summary
Constructors Constructor Description NetworkInstanceProtocolBuilder()
NetworkInstanceProtocolBuilder(BgpTop arg)
NetworkInstanceProtocolBuilder(NetworkInstanceProtocol base)
-
Method Summary
All Methods Instance Methods Concrete Methods Modifier and Type Method Description NetworkInstanceProtocol
build()
void
fieldsFrom(org.opendaylight.yangtools.yang.binding.DataObject arg)
Set fields from given grouping argument.Bgp
getBgp()
NetworkInstanceProtocolBuilder
setBgp(Bgp value)
-
-
-
Constructor Detail
-
NetworkInstanceProtocolBuilder
public NetworkInstanceProtocolBuilder()
-
NetworkInstanceProtocolBuilder
public NetworkInstanceProtocolBuilder(BgpTop arg)
-
NetworkInstanceProtocolBuilder
public NetworkInstanceProtocolBuilder(NetworkInstanceProtocol 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.rev151009.BgpTop
- Parameters:
arg
- grouping object- Throws:
IllegalArgumentException
- if given argument is none of valid types or has property with incompatible value
-
getBgp
public Bgp getBgp()
-
setBgp
public NetworkInstanceProtocolBuilder setBgp(Bgp value)
-
build
public NetworkInstanceProtocol build()
- Specified by:
build
in interfaceorg.opendaylight.yangtools.concepts.Builder<NetworkInstanceProtocol>
- Specified by:
build
in interfaceorg.opendaylight.yangtools.concepts.CheckedBuilder<NetworkInstanceProtocol,IllegalArgumentException>
-
-