Interface Configuration.Builder
-
- All Known Implementing Classes:
ConfigurationImpl.BuilderImpl
- Enclosing interface:
- Configuration
public static interface Configuration.Builder
-
-
Method Summary
All Methods Instance Methods Abstract Methods Default Methods Deprecated Methods Modifier and Type Method Description Configuration.AnnotationsConfig.BuilderannotationsConfig()Configurationbuild()Configuration.BuildermaxNestedMessageDepth(int maxNestedMessageDepth)Configuration.BuildersetLogOutOfSequenceReads(boolean logOutOfSequenceReads)Configuration.BuildersetLogOutOfSequenceWrites(boolean logOutOfSequenceWrites)default Configuration.BuildersetLogUndefinedAnnotations(boolean logUndefinedAnnotations)Configuration.WrappingConfig.BuilderwrappingConfig()
-
-
-
Method Detail
-
setLogOutOfSequenceReads
Configuration.Builder setLogOutOfSequenceReads(boolean logOutOfSequenceReads)
-
setLogOutOfSequenceWrites
Configuration.Builder setLogOutOfSequenceWrites(boolean logOutOfSequenceWrites)
-
maxNestedMessageDepth
Configuration.Builder maxNestedMessageDepth(int maxNestedMessageDepth)
-
setLogUndefinedAnnotations
@Deprecated default Configuration.Builder setLogUndefinedAnnotations(boolean logUndefinedAnnotations)
Should we log a warning every time we encounter an undefined documentation annotation? This istrueby default.
-
wrappingConfig
Configuration.WrappingConfig.Builder wrappingConfig()
-
annotationsConfig
Configuration.AnnotationsConfig.Builder annotationsConfig()
-
build
Configuration build()
-
-