org.opendaylight.yang.gen.v1.urn.opendaylight.flow.types.port.rev130925.multipart.reply.multipart.reply.body

Class MultipartReplyPortDescBuilder

java.lang.Object

org.opendaylight.yang.gen.v1.urn.opendaylight.flow.types.port.rev130925.multipart.reply.multipart.reply.body.MultipartReplyPortDescBuilder

All Implemented Interfaces:

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

public class MultipartReplyPortDescBuilder
extends Object
implements org.opendaylight.yangtools.concepts.Builder<MultipartReplyPortDesc>

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

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

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

MultipartReplyPortDescBuilder, Builder

Constructor Summary

Constructors

Constructor and Description
MultipartReplyPortDescBuilder()
MultipartReplyPortDescBuilder(MultipartReplyPortDesc base)

Method Summary

Modifier and Type	Method and Description
MultipartReplyPortDescBuilder	addAugmentation(Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<MultipartReplyPortDesc>> augmentationType, org.opendaylight.yangtools.yang.binding.Augmentation<MultipartReplyPortDesc> augmentationValue)
<E$$ extends org.opendaylight.yangtools.yang.binding.Augmentation<MultipartReplyPortDesc>> E$$	augmentation(Class<E$$> augmentationType)
MultipartReplyPortDesc	build()
List<Ports>	getPorts()
MultipartReplyPortDescBuilder	removeAugmentation(Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<MultipartReplyPortDesc>> augmentationType)
MultipartReplyPortDescBuilder	setPorts(List<Ports> values)

Methods inherited from class java.lang.Object

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

Constructor Detail

MultipartReplyPortDescBuilder

public MultipartReplyPortDescBuilder()

MultipartReplyPortDescBuilder

public MultipartReplyPortDescBuilder(MultipartReplyPortDesc base)

Method Detail

getPorts

public List<Ports> getPorts()

augmentation

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

setPorts

public MultipartReplyPortDescBuilder setPorts(List<Ports> values)

addAugmentation

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

removeAugmentation

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

build

public MultipartReplyPortDesc build()

Specified by:

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