Package org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.bgp.flowspec.rev200120.flowspec.destination.group.ipv6.flowspec.flowspec.type

Class DestinationIpv6PrefixCaseBuilder

  • All Implemented Interfaces:
    org.opendaylight.yangtools.concepts.Builder<DestinationIpv6PrefixCase>, org.opendaylight.yangtools.concepts.CheckedBuilder<DestinationIpv6PrefixCase,​IllegalArgumentException>, org.opendaylight.yangtools.concepts.Mutable, org.opendaylight.yangtools.concepts.MutationBehaviour<org.opendaylight.yangtools.concepts.Mutable>
    @Generated("mdsal-binding-generator")
public class DestinationIpv6PrefixCaseBuilder
extends Object
implements org.opendaylight.yangtools.concepts.Builder<DestinationIpv6PrefixCase>
    Class that builds DestinationIpv6PrefixCase 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: 

       
     DestinationIpv6PrefixCase createDestinationIpv6PrefixCase(int fooXyzzy, int barBaz) {
         return new DestinationIpv6PrefixCaseBuilder()
             .setFoo(new FooBuilder().setXyzzy(fooXyzzy).build())
             .setBar(new BarBuilder().setBaz(barBaz).build())
             .build();
     }

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

    • Constructor Detail

      • DestinationIpv6PrefixCaseBuilder

        public DestinationIpv6PrefixCaseBuilder()

    • Method Detail

      • getDestinationPrefix

        public org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.ietf.inet.types.rev130715.Ipv6Prefix getDestinationPrefix()

      • augmentation

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

      • setDestinationPrefix

        public DestinationIpv6PrefixCaseBuilder setDestinationPrefix​(org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.ietf.inet.types.rev130715.Ipv6Prefix value)

      • removeAugmentation

        public DestinationIpv6PrefixCaseBuilder removeAugmentation​(Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<DestinationIpv6PrefixCase>> augmentationType)
        Remove an augmentation from this builder's product. If this builder does not track such an augmentation type, this method does nothing.
        Parameters:
        augmentationType - augmentation type to be removed
        Returns:
        this builder