Class NeighborTransportStateAugmentationBuilder

  • All Implemented Interfaces:
    org.opendaylight.yangtools.concepts.Builder<NeighborTransportStateAugmentation>, org.opendaylight.yangtools.concepts.CheckedBuilder<NeighborTransportStateAugmentation,​IllegalArgumentException>, org.opendaylight.yangtools.concepts.Mutable, org.opendaylight.yangtools.concepts.MutationBehaviour<org.opendaylight.yangtools.concepts.Mutable>

    @Generated("mdsal-binding-generator")
    public class NeighborTransportStateAugmentationBuilder
    extends Object
    implements org.opendaylight.yangtools.concepts.Builder<NeighborTransportStateAugmentation>
    Class that builds NeighborTransportStateAugmentation 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:

       
         NeighborTransportStateAugmentation createNeighborTransportStateAugmentation(int fooXyzzy, int barBaz) {
             return new NeighborTransportStateAugmentationBuilder()
                 .setFoo(new FooBuilder().setXyzzy(fooXyzzy).build())
                 .setBar(new BarBuilder().setBaz(barBaz).build())
                 .build();
         }
       
     

    This pattern is supported by the immutable nature of NeighborTransportStateAugmentation, 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:
    NeighborTransportStateAugmentation, Builder
    • Constructor Detail

      • NeighborTransportStateAugmentationBuilder

        public NeighborTransportStateAugmentationBuilder()
      • NeighborTransportStateAugmentationBuilder

        public NeighborTransportStateAugmentationBuilder​(BgpNeighborTransportState arg)
    • 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:
        • BgpNeighborTransportState
        Parameters:
        arg - grouping object
        Throws:
        IllegalArgumentException - if given argument is none of valid types or has property with incompatible value
      • getLocalPort

        public org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.ietf.inet.types.rev130715.PortNumber getLocalPort()
      • getRemoteAddress

        public org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.ietf.inet.types.rev130715.IpAddress getRemoteAddress()
      • getRemotePort

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