org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.pcep.types.rev181109.pcreq.message.pcreq.message.requests.segment.computation.p2mp.endpoint.rro.pair

Class RrosBuilder

java.lang.Object

org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.pcep.types.rev181109.pcreq.message.pcreq.message.requests.segment.computation.p2mp.endpoint.rro.pair.RrosBuilder

All Implemented Interfaces:

org.opendaylight.yangtools.concepts.Builder<Rros>, org.opendaylight.yangtools.concepts.CheckedBuilder<Rros,IllegalArgumentException>, org.opendaylight.yangtools.concepts.Mutable, org.opendaylight.yangtools.concepts.MutationBehaviour<org.opendaylight.yangtools.concepts.Mutable>

public class RrosBuilder
extends Object
implements org.opendaylight.yangtools.concepts.Builder<Rros>

Class that builds RrosBuilder 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:

   
     RrosBuilder createTarget(int fooXyzzy, int barBaz) {
         return new RrosBuilderBuilder()
             .setFoo(new FooBuilder().setXyzzy(fooXyzzy).build())
             .setBar(new BarBuilder().setBaz(barBaz).build())
             .build();
     }
   
 

This pattern is supported by the immutable nature of RrosBuilder, 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:

RrosBuilder, Builder

Constructor Summary

Constructors

Constructor and Description
RrosBuilder()
RrosBuilder(Rros base)

Method Summary

Modifier and Type	Method and Description
RrosBuilder	addAugmentation(Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<Rros>> augmentationType, org.opendaylight.yangtools.yang.binding.Augmentation<Rros> augmentationValue)
<E$$ extends org.opendaylight.yangtools.yang.binding.Augmentation<Rros>> E$$	augmentation(Class<E$$> augmentationType)
Rros	build()
RouteObject	getRouteObject()
RrosBuilder	removeAugmentation(Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<Rros>> augmentationType)
RrosBuilder	setRouteObject(RouteObject value)

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

RrosBuilder

public RrosBuilder()

RrosBuilder

public RrosBuilder(Rros base)

Method Detail

getRouteObject

public RouteObject getRouteObject()

augmentation

public <E$$ extends org.opendaylight.yangtools.yang.binding.Augmentation<Rros>> E$$ augmentation(Class<E$$> augmentationType)

setRouteObject

public RrosBuilder setRouteObject(RouteObject value)

addAugmentation

public RrosBuilder addAugmentation(Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<Rros>> augmentationType,
                                   org.opendaylight.yangtools.yang.binding.Augmentation<Rros> augmentationValue)

removeAugmentation

public RrosBuilder removeAugmentation(Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<Rros>> augmentationType)

build

public Rros build()

Specified by:

build in interface org.opendaylight.yangtools.concepts.CheckedBuilder<Rros,IllegalArgumentException>