Class LoggingBuilder
- java.lang.Object
-
- org.opendaylight.yang.gen.v1.urn.ericsson.params.xml.ns.yang.ebgp.rev150901.bgp.LoggingBuilder
-
- All Implemented Interfaces:
org.opendaylight.yangtools.concepts.Builder<Logging>
,org.opendaylight.yangtools.concepts.CheckedBuilder<Logging,java.lang.IllegalArgumentException>
,org.opendaylight.yangtools.concepts.Mutable
,org.opendaylight.yangtools.concepts.MutationBehaviour<org.opendaylight.yangtools.concepts.Mutable>
@Generated("mdsal-binding-generator") public class LoggingBuilder extends java.lang.Object implements org.opendaylight.yangtools.concepts.Builder<Logging>
Class that buildsLoggingBuilder
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:
LoggingBuilder createTarget(int fooXyzzy, int barBaz) { return new LoggingBuilderBuilder() .setFoo(new FooBuilder().setXyzzy(fooXyzzy).build()) .setBar(new BarBuilder().setBaz(barBaz).build()) .build(); }
This pattern is supported by the immutable nature of LoggingBuilder, 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:
LoggingBuilder
,Builder
-
-
Constructor Summary
Constructors Constructor Description LoggingBuilder()
LoggingBuilder(Logging base)
-
Method Summary
All Methods Instance Methods Concrete Methods Modifier and Type Method Description LoggingBuilder
addAugmentation(org.opendaylight.yangtools.yang.binding.Augmentation<Logging> augmentation)
Add an augmentation to this builder's product.<E$$ extends org.opendaylight.yangtools.yang.binding.Augmentation<Logging>>
E$$augmentation(java.lang.Class<E$$> augmentationType)
Logging
build()
java.lang.String
getFile()
java.lang.String
getLevel()
LoggingBuilder
removeAugmentation(java.lang.Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<Logging>> augmentationType)
Remove an augmentation from this builder's product.LoggingBuilder
setFile(java.lang.String value)
LoggingBuilder
setLevel(java.lang.String value)
-
-
-
Constructor Detail
-
LoggingBuilder
public LoggingBuilder()
-
LoggingBuilder
public LoggingBuilder(Logging base)
-
-
Method Detail
-
getFile
public java.lang.String getFile()
-
getLevel
public java.lang.String getLevel()
-
augmentation
public <E$$ extends org.opendaylight.yangtools.yang.binding.Augmentation<Logging>> E$$ augmentation(java.lang.Class<E$$> augmentationType)
-
setFile
public LoggingBuilder setFile(java.lang.String value)
-
setLevel
public LoggingBuilder setLevel(java.lang.String value)
-
addAugmentation
public LoggingBuilder addAugmentation(org.opendaylight.yangtools.yang.binding.Augmentation<Logging> augmentation)
Add an augmentation to this builder's product.- Parameters:
augmentation
- augmentation to be added- Returns:
- this builder
- Throws:
java.lang.NullPointerException
- ifaugmentation
is null
-
removeAugmentation
public LoggingBuilder removeAugmentation(java.lang.Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<Logging>> augmentationType)
Remove an augmentation from this builder's product. If this builder does not track such an augmentation type, this method does nothing.- Parameters:
augmentationType
- augmentation type to be removed- Returns:
- this builder
-
-