org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.pcep.types.rev181109.pcrep.message.pcrep.message.replies.result.failure._case.no.path.tlvs

Class NoPathVectorBuilder

java.lang.Object

org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.pcep.types.rev181109.pcrep.message.pcrep.message.replies.result.failure._case.no.path.tlvs.NoPathVectorBuilder

All Implemented Interfaces:

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

public class NoPathVectorBuilder
extends Object
implements org.opendaylight.yangtools.concepts.Builder<NoPathVector>

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

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

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

NoPathVectorBuilder, Builder

Constructor Summary

Constructors

Constructor and Description
NoPathVectorBuilder()
NoPathVectorBuilder(NoPathVector base)
NoPathVectorBuilder(NoPathVectorTlv arg)
NoPathVectorBuilder(Tlv arg)

Method Summary

Modifier and Type	Method and Description
NoPathVectorBuilder	addAugmentation(Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<NoPathVector>> augmentationType, org.opendaylight.yangtools.yang.binding.Augmentation<NoPathVector> augmentationValue)
<E$$ extends org.opendaylight.yangtools.yang.binding.Augmentation<NoPathVector>> E$$	augmentation(Class<E$$> augmentationType)
NoPathVector	build()
void	fieldsFrom(org.opendaylight.yangtools.yang.binding.DataObject arg) Set fields from given grouping argument.
NoPathVectorTlv.Flags	getFlags()
NoPathVectorBuilder	removeAugmentation(Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<NoPathVector>> augmentationType)
NoPathVectorBuilder	setFlags(NoPathVectorTlv.Flags value)

Methods inherited from class java.lang.Object

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

Constructor Detail

NoPathVectorBuilder

public NoPathVectorBuilder()

NoPathVectorBuilder

public NoPathVectorBuilder(NoPathVectorTlv arg)

NoPathVectorBuilder

public NoPathVectorBuilder(Tlv arg)

NoPathVectorBuilder

public NoPathVectorBuilder(NoPathVector 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.urn.opendaylight.params.xml.ns.yang.pcep.types.rev181109.Tlv
• org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.pcep.types.rev181109.NoPathVectorTlv

Parameters:

arg - grouping object

Throws:

IllegalArgumentException - if given argument is none of valid types

getFlags

public NoPathVectorTlv.Flags getFlags()

augmentation

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

setFlags

public NoPathVectorBuilder setFlags(NoPathVectorTlv.Flags value)

addAugmentation

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

removeAugmentation

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

build

public NoPathVector build()

Specified by:

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