Package org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.bgp.flowspec.rev200120.bgp.rib.rib.peer.effective.rib.in.tables.routes

Class FlowspecRoutesCaseBuilder

java.lang.Object
org.opendaylight.yangtools.binding.lib.AugmentableBuilder<FlowspecRoutesCase,FlowspecRoutesCaseBuilder>
org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.bgp.flowspec.rev200120.bgp.rib.rib.peer.effective.rib.in.tables.routes.FlowspecRoutesCaseBuilder
All Implemented Interfaces:
org.opendaylight.yangtools.concepts.Mutable
@Generated("mdsal-binding-generator") public class FlowspecRoutesCaseBuilder extends org.opendaylight.yangtools.binding.lib.AugmentableBuilder<FlowspecRoutesCase,FlowspecRoutesCaseBuilder>
Class that builds FlowspecRoutesCase 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: 

   
     FlowspecRoutesCase createFlowspecRoutesCase(int fooXyzzy, int barBaz) {
         return new FlowspecRoutesCaseBuilder()
             .setFoo(new FooBuilder().setXyzzy(fooXyzzy).build())
             .setBar(new BarBuilder().setBaz(barBaz).build())
             .build();
     }

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

    • FlowspecRoutesCaseBuilder

      public FlowspecRoutesCaseBuilder()
      Construct an empty builder.

    • FlowspecRoutesCaseBuilder

      public FlowspecRoutesCaseBuilder(FlowspecRoutes arg)
      Construct a new builder initialized from specified FlowspecRoutes.
      Parameters:
      arg - org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.bgp.flowspec.rev200120.FlowspecRoutes from which the builder should be initialized

    • FlowspecRoutesCaseBuilder

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

  • Method Details