Package org.opendaylight.yang.gen.v1.urn.opendaylight.genius.interfacemanager.servicebinding.rev160406.service.bindings.services.info.bound.services.instruction.instruction.apply.actions._case.apply.actions.action.action

Class ServiceBindingNxActionOutputRegApplyActionsCaseBuilder

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

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

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

    • Constructor Detail

      • ServiceBindingNxActionOutputRegApplyActionsCaseBuilder

        public ServiceBindingNxActionOutputRegApplyActionsCaseBuilder()

      • ServiceBindingNxActionOutputRegApplyActionsCaseBuilder

        public ServiceBindingNxActionOutputRegApplyActionsCaseBuilder​(org.opendaylight.yang.gen.v1.urn.opendaylight.openflowplugin.extension.nicira.action.rev140714.NxActionOutputRegGrouping 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.openflowplugin.extension.nicira.action.rev140714.NxActionOutputRegGrouping
        Parameters:
        arg - grouping object
        Throws:
        java.lang.IllegalArgumentException - if given argument is none of valid types or has property with incompatible value

      • getNxOutputReg

        public org.opendaylight.yang.gen.v1.urn.opendaylight.openflowplugin.extension.nicira.action.rev140714.nx.action.output.reg.grouping.NxOutputReg getNxOutputReg()