Package org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.topology.pcep.programming.rev181109

Class SubmitRemoveLspInputBuilder

java.lang.Object
org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.topology.pcep.programming.rev181109.SubmitRemoveLspInputBuilder
@Generated("mdsal-binding-generator") public class SubmitRemoveLspInputBuilder extends Object
Class that builds SubmitRemoveLspInput 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: 

   
     SubmitRemoveLspInput createSubmitRemoveLspInput(int fooXyzzy, int barBaz) {
         return new SubmitRemoveLspInputBuilder()
             .setFoo(new FooBuilder().setXyzzy(fooXyzzy).build())
             .setBar(new BarBuilder().setBaz(barBaz).build())
             .build();
     }

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

  • Constructor Details

    • SubmitRemoveLspInputBuilder

      public SubmitRemoveLspInputBuilder()
      Construct an empty builder.

    • SubmitRemoveLspInputBuilder

      public SubmitRemoveLspInputBuilder(TopologyInstructionInput arg)
      Construct a new builder initialized from specified TopologyInstructionInput.
      Parameters:
      arg - TopologyInstructionInput from which the builder should be initialized

    • SubmitRemoveLspInputBuilder

      public SubmitRemoveLspInputBuilder(SubmitInstructionInput arg)
      Construct a new builder initialized from specified SubmitInstructionInput.
      Parameters:
      arg - SubmitInstructionInput from which the builder should be initialized

    • SubmitRemoveLspInputBuilder

      public SubmitRemoveLspInputBuilder(NetworkTopologyReference arg)
      Construct a new builder initialized from specified NetworkTopologyReference.
      Parameters:
      arg - NetworkTopologyReference from which the builder should be initialized

    • SubmitRemoveLspInputBuilder

      public SubmitRemoveLspInputBuilder(RemoveLspArgs arg)
      Construct a new builder initialized from specified RemoveLspArgs.
      Parameters:
      arg - RemoveLspArgs from which the builder should be initialized

    • SubmitRemoveLspInputBuilder

      public SubmitRemoveLspInputBuilder(LspId arg)
      Construct a new builder initialized from specified LspId.
      Parameters:
      arg - LspId from which the builder should be initialized

    • SubmitRemoveLspInputBuilder

      public SubmitRemoveLspInputBuilder(NodeId arg)
      Construct a new builder initialized from specified NodeId.
      Parameters:
      arg - org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.topology.pcep.rev220730.NodeId from which the builder should be initialized

    • SubmitRemoveLspInputBuilder

      public SubmitRemoveLspInputBuilder(SubmitRemoveLspInput base)
      Construct a builder initialized with state from specified SubmitRemoveLspInput.
      Parameters:
      base - SubmitRemoveLspInput from which the builder should be initialized

  • Method Details