Class SendNeighborSolicitationInputBuilder

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

    public class SendNeighborSolicitationInputBuilder
    extends java.lang.Object
    implements org.opendaylight.yangtools.concepts.Builder<SendNeighborSolicitationInput>
    Class that builds SendNeighborSolicitationInputBuilder 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:

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

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

      • SendNeighborSolicitationInputBuilder

        public SendNeighborSolicitationInputBuilder()
      • SendNeighborSolicitationInputBuilder

        public SendNeighborSolicitationInputBuilder​(Interfaces 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:
        • org.opendaylight.yang.gen.v1.urn.opendaylight.genius.ipv6.nd.util.rev170210.Interfaces
        Parameters:
        arg - grouping object
        Throws:
        java.lang.IllegalArgumentException - if given argument is none of valid types
      • getInterfaceAddress

        public java.util.List<InterfaceAddress> getInterfaceAddress()
      • getTargetIpAddress

        public org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.ietf.inet.types.rev130715.Ipv6Address getTargetIpAddress()
      • augmentation

        public <E$$ extends org.opendaylight.yangtools.yang.binding.Augmentation<SendNeighborSolicitationInput>> E$$ augmentation​(java.lang.Class<E$$> augmentationType)
      • setTargetIpAddress

        public SendNeighborSolicitationInputBuilder setTargetIpAddress​(org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.ietf.inet.types.rev130715.Ipv6Address value)