org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.pcep.types.rev181109.pcreq.message.pcreq.message.requests

Class SegmentComputationBuilder

java.lang.Object

org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.pcep.types.rev181109.pcreq.message.pcreq.message.requests.SegmentComputationBuilder

All Implemented Interfaces:

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

public class SegmentComputationBuilder
extends Object
implements org.opendaylight.yangtools.concepts.Builder<SegmentComputation>

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

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

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

SegmentComputationBuilder, Builder

Constructor Summary

Constructors

Constructor and Description
SegmentComputationBuilder()
SegmentComputationBuilder(SegmentComputation base)

Method Summary

Modifier and Type	Method and Description
SegmentComputationBuilder	addAugmentation(Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<SegmentComputation>> augmentationType, org.opendaylight.yangtools.yang.binding.Augmentation<SegmentComputation> augmentationValue)
<E$$ extends org.opendaylight.yangtools.yang.binding.Augmentation<SegmentComputation>> E$$	augmentation(Class<E$$> augmentationType)
SegmentComputation	build()
P2mp	getP2mp()
P2p	getP2p()
SegmentComputationBuilder	removeAugmentation(Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<SegmentComputation>> augmentationType)
SegmentComputationBuilder	setP2mp(P2mp value)
SegmentComputationBuilder	setP2p(P2p value)

Methods inherited from class java.lang.Object

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

Constructor Detail

SegmentComputationBuilder

public SegmentComputationBuilder()

SegmentComputationBuilder

public SegmentComputationBuilder(SegmentComputation base)

Method Detail

getP2mp

public P2mp getP2mp()

getP2p

public P2p getP2p()

augmentation

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

setP2mp

public SegmentComputationBuilder setP2mp(P2mp value)

setP2p

public SegmentComputationBuilder setP2p(P2p value)

addAugmentation

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

removeAugmentation

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

build

public SegmentComputation build()

Specified by:

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