Package org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.pcep.types.rev181109.pcerr.message.pcerr.message.error.type.request._case

Class RequestBuilder

java.lang.Object

org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.pcep.types.rev181109.pcerr.message.pcerr.message.error.type.request._case.RequestBuilder

All Implemented Interfaces:

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

public class RequestBuilder
extends Object
implements org.opendaylight.yangtools.concepts.Builder<Request>

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

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

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

RequestBuilder, Builder

Constructor Summary

Constructors

Constructor	Description
RequestBuilder()
RequestBuilder(Request base)

Method Summary

Modifier and Type	Method	Description
RequestBuilder	addAugmentation(Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<Request>> augmentationType, org.opendaylight.yangtools.yang.binding.Augmentation<Request> augmentationValue)
<E$$ extends org.opendaylight.yangtools.yang.binding.Augmentation<Request>> E$$	augmentation(Class<E$$> augmentationType)
Request	build()
List<Rps>	getRps()
RequestBuilder	removeAugmentation(Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<Request>> augmentationType)
RequestBuilder	setRps(List<Rps> values)

Methods inherited from class java.lang.Object

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

Constructor Detail

RequestBuilder

public RequestBuilder()

RequestBuilder

public RequestBuilder(Request base)

Method Detail

getRps

public List<Rps> getRps()

augmentation

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

setRps

public RequestBuilder setRps(List<Rps> values)

addAugmentation

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

removeAugmentation

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

build

public Request build()

Specified by:

build in interface org.opendaylight.yangtools.concepts.Builder<Request>

Specified by:

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