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

Class RequestCaseBuilder

java.lang.Object

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

All Implemented Interfaces:

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

public class RequestCaseBuilder
extends Object
implements org.opendaylight.yangtools.concepts.Builder<RequestCase>

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

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

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

RequestCaseBuilder, Builder

Constructor Summary

Constructors

Constructor and Description
RequestCaseBuilder()
RequestCaseBuilder(RequestCase base)

Method Summary

Modifier and Type	Method and Description
RequestCaseBuilder	addAugmentation(Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<RequestCase>> augmentationType, org.opendaylight.yangtools.yang.binding.Augmentation<RequestCase> augmentationValue)
<E$$ extends org.opendaylight.yangtools.yang.binding.Augmentation<RequestCase>> E$$	augmentation(Class<E$$> augmentationType)
RequestCase	build()
Request	getRequest()
RequestCaseBuilder	removeAugmentation(Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<RequestCase>> augmentationType)
RequestCaseBuilder	setRequest(Request value)

Methods inherited from class java.lang.Object

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

Constructor Detail

RequestCaseBuilder

public RequestCaseBuilder()

RequestCaseBuilder

public RequestCaseBuilder(RequestCase base)

Method Detail

getRequest

public Request getRequest()

augmentation

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

setRequest

public RequestCaseBuilder setRequest(Request value)

addAugmentation

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

removeAugmentation

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

build

public RequestCase build()

Specified by:

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