Class DescriptorProtos.MessageOptions.Builder

    • Method Detail

      • getDescriptor

        public static final com.google.protobuf.Descriptors.Descriptor getDescriptor()
      • internalGetFieldAccessorTable

        protected com.google.protobuf.GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()
        Specified by:
        internalGetFieldAccessorTable in class com.google.protobuf.GeneratedMessageV3.Builder<DescriptorProtos.MessageOptions.Builder>
      • getDescriptorForType

        public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()
        Specified by:
        getDescriptorForType in interface com.google.protobuf.Message.Builder
        Specified by:
        getDescriptorForType in interface com.google.protobuf.MessageOrBuilder
        Overrides:
        getDescriptorForType in class com.google.protobuf.GeneratedMessageV3.Builder<DescriptorProtos.MessageOptions.Builder>
      • getDefaultInstanceForType

        public DescriptorProtos.MessageOptions getDefaultInstanceForType()
        Specified by:
        getDefaultInstanceForType in interface com.google.protobuf.GeneratedMessageV3.ExtendableMessageOrBuilder<DescriptorProtos.MessageOptions>
        Specified by:
        getDefaultInstanceForType in interface com.google.protobuf.MessageLiteOrBuilder
        Specified by:
        getDefaultInstanceForType in interface com.google.protobuf.MessageOrBuilder
      • build

        public DescriptorProtos.MessageOptions build()
        Specified by:
        build in interface com.google.protobuf.Message.Builder
        Specified by:
        build in interface com.google.protobuf.MessageLite.Builder
      • buildPartial

        public DescriptorProtos.MessageOptions buildPartial()
        Specified by:
        buildPartial in interface com.google.protobuf.Message.Builder
        Specified by:
        buildPartial in interface com.google.protobuf.MessageLite.Builder
      • mergeFrom

        public DescriptorProtos.MessageOptions.Builder mergeFrom​(com.google.protobuf.CodedInputStream input,
                                                                 com.google.protobuf.ExtensionRegistryLite extensionRegistry)
                                                          throws java.io.IOException
        Specified by:
        mergeFrom in interface com.google.protobuf.Message.Builder
        Specified by:
        mergeFrom in interface com.google.protobuf.MessageLite.Builder
        Overrides:
        mergeFrom in class com.google.protobuf.AbstractMessage.Builder<DescriptorProtos.MessageOptions.Builder>
        Throws:
        java.io.IOException
      • hasMessageSetWireFormat

        public boolean hasMessageSetWireFormat()
         Set true to use the old proto1 MessageSet wire format for extensions.
         This is provided for backwards-compatibility with the MessageSet wire
         format.  You should not use this for any other reason:  It's less
         efficient, has fewer features, and is more complicated.
         The message must be defined exactly as follows:
           message Foo {
             option message_set_wire_format = true;
             extensions 4 to max;
           }
         Note that the message cannot have any defined fields; MessageSets only
         have extensions.
         All extensions of your type must be singular messages; e.g. they cannot
         be int32s, enums, or repeated messages.
         Because this is an option, the above two restrictions are not enforced by
         the protocol compiler.
         
        optional bool message_set_wire_format = 1 [default = false];
        Specified by:
        hasMessageSetWireFormat in interface DescriptorProtos.MessageOptionsOrBuilder
        Returns:
        Whether the messageSetWireFormat field is set.
      • getMessageSetWireFormat

        public boolean getMessageSetWireFormat()
         Set true to use the old proto1 MessageSet wire format for extensions.
         This is provided for backwards-compatibility with the MessageSet wire
         format.  You should not use this for any other reason:  It's less
         efficient, has fewer features, and is more complicated.
         The message must be defined exactly as follows:
           message Foo {
             option message_set_wire_format = true;
             extensions 4 to max;
           }
         Note that the message cannot have any defined fields; MessageSets only
         have extensions.
         All extensions of your type must be singular messages; e.g. they cannot
         be int32s, enums, or repeated messages.
         Because this is an option, the above two restrictions are not enforced by
         the protocol compiler.
         
        optional bool message_set_wire_format = 1 [default = false];
        Specified by:
        getMessageSetWireFormat in interface DescriptorProtos.MessageOptionsOrBuilder
        Returns:
        The messageSetWireFormat.
      • setMessageSetWireFormat

        public DescriptorProtos.MessageOptions.Builder setMessageSetWireFormat​(boolean value)
         Set true to use the old proto1 MessageSet wire format for extensions.
         This is provided for backwards-compatibility with the MessageSet wire
         format.  You should not use this for any other reason:  It's less
         efficient, has fewer features, and is more complicated.
         The message must be defined exactly as follows:
           message Foo {
             option message_set_wire_format = true;
             extensions 4 to max;
           }
         Note that the message cannot have any defined fields; MessageSets only
         have extensions.
         All extensions of your type must be singular messages; e.g. they cannot
         be int32s, enums, or repeated messages.
         Because this is an option, the above two restrictions are not enforced by
         the protocol compiler.
         
        optional bool message_set_wire_format = 1 [default = false];
        Parameters:
        value - The messageSetWireFormat to set.
        Returns:
        This builder for chaining.
      • clearMessageSetWireFormat

        public DescriptorProtos.MessageOptions.Builder clearMessageSetWireFormat()
         Set true to use the old proto1 MessageSet wire format for extensions.
         This is provided for backwards-compatibility with the MessageSet wire
         format.  You should not use this for any other reason:  It's less
         efficient, has fewer features, and is more complicated.
         The message must be defined exactly as follows:
           message Foo {
             option message_set_wire_format = true;
             extensions 4 to max;
           }
         Note that the message cannot have any defined fields; MessageSets only
         have extensions.
         All extensions of your type must be singular messages; e.g. they cannot
         be int32s, enums, or repeated messages.
         Because this is an option, the above two restrictions are not enforced by
         the protocol compiler.
         
        optional bool message_set_wire_format = 1 [default = false];
        Returns:
        This builder for chaining.
      • hasNoStandardDescriptorAccessor

        public boolean hasNoStandardDescriptorAccessor()
         Disables the generation of the standard "descriptor()" accessor, which can
         conflict with a field of the same name.  This is meant to make migration
         from proto1 easier; new code should avoid fields named "descriptor".
         
        optional bool no_standard_descriptor_accessor = 2 [default = false];
        Specified by:
        hasNoStandardDescriptorAccessor in interface DescriptorProtos.MessageOptionsOrBuilder
        Returns:
        Whether the noStandardDescriptorAccessor field is set.
      • getNoStandardDescriptorAccessor

        public boolean getNoStandardDescriptorAccessor()
         Disables the generation of the standard "descriptor()" accessor, which can
         conflict with a field of the same name.  This is meant to make migration
         from proto1 easier; new code should avoid fields named "descriptor".
         
        optional bool no_standard_descriptor_accessor = 2 [default = false];
        Specified by:
        getNoStandardDescriptorAccessor in interface DescriptorProtos.MessageOptionsOrBuilder
        Returns:
        The noStandardDescriptorAccessor.
      • setNoStandardDescriptorAccessor

        public DescriptorProtos.MessageOptions.Builder setNoStandardDescriptorAccessor​(boolean value)
         Disables the generation of the standard "descriptor()" accessor, which can
         conflict with a field of the same name.  This is meant to make migration
         from proto1 easier; new code should avoid fields named "descriptor".
         
        optional bool no_standard_descriptor_accessor = 2 [default = false];
        Parameters:
        value - The noStandardDescriptorAccessor to set.
        Returns:
        This builder for chaining.
      • clearNoStandardDescriptorAccessor

        public DescriptorProtos.MessageOptions.Builder clearNoStandardDescriptorAccessor()
         Disables the generation of the standard "descriptor()" accessor, which can
         conflict with a field of the same name.  This is meant to make migration
         from proto1 easier; new code should avoid fields named "descriptor".
         
        optional bool no_standard_descriptor_accessor = 2 [default = false];
        Returns:
        This builder for chaining.
      • hasDeprecated

        public boolean hasDeprecated()
         Is this message deprecated?
         Depending on the target platform, this can emit Deprecated annotations
         for the message, or it will be completely ignored; in the very least,
         this is a formalization for deprecating messages.
         
        optional bool deprecated = 3 [default = false];
        Specified by:
        hasDeprecated in interface DescriptorProtos.MessageOptionsOrBuilder
        Returns:
        Whether the deprecated field is set.
      • getDeprecated

        public boolean getDeprecated()
         Is this message deprecated?
         Depending on the target platform, this can emit Deprecated annotations
         for the message, or it will be completely ignored; in the very least,
         this is a formalization for deprecating messages.
         
        optional bool deprecated = 3 [default = false];
        Specified by:
        getDeprecated in interface DescriptorProtos.MessageOptionsOrBuilder
        Returns:
        The deprecated.
      • setDeprecated

        public DescriptorProtos.MessageOptions.Builder setDeprecated​(boolean value)
         Is this message deprecated?
         Depending on the target platform, this can emit Deprecated annotations
         for the message, or it will be completely ignored; in the very least,
         this is a formalization for deprecating messages.
         
        optional bool deprecated = 3 [default = false];
        Parameters:
        value - The deprecated to set.
        Returns:
        This builder for chaining.
      • clearDeprecated

        public DescriptorProtos.MessageOptions.Builder clearDeprecated()
         Is this message deprecated?
         Depending on the target platform, this can emit Deprecated annotations
         for the message, or it will be completely ignored; in the very least,
         this is a formalization for deprecating messages.
         
        optional bool deprecated = 3 [default = false];
        Returns:
        This builder for chaining.
      • hasMapEntry

        public boolean hasMapEntry()
         Whether the message is an automatically generated map entry type for the
         maps field.
         For maps fields:
             map<KeyType, ValueType> map_field = 1;
         The parsed descriptor looks like:
             message MapFieldEntry {
                 option map_entry = true;
                 optional KeyType key = 1;
                 optional ValueType value = 2;
             }
             repeated MapFieldEntry map_field = 1;
         Implementations may choose not to generate the map_entry=true message, but
         use a native map in the target language to hold the keys and values.
         The reflection APIs in such implementations still need to work as
         if the field is a repeated message field.
         NOTE: Do not set the option in .proto files. Always use the maps syntax
         instead. The option should only be implicitly set by the proto compiler
         parser.
         
        optional bool map_entry = 7;
        Specified by:
        hasMapEntry in interface DescriptorProtos.MessageOptionsOrBuilder
        Returns:
        Whether the mapEntry field is set.
      • getMapEntry

        public boolean getMapEntry()
         Whether the message is an automatically generated map entry type for the
         maps field.
         For maps fields:
             map<KeyType, ValueType> map_field = 1;
         The parsed descriptor looks like:
             message MapFieldEntry {
                 option map_entry = true;
                 optional KeyType key = 1;
                 optional ValueType value = 2;
             }
             repeated MapFieldEntry map_field = 1;
         Implementations may choose not to generate the map_entry=true message, but
         use a native map in the target language to hold the keys and values.
         The reflection APIs in such implementations still need to work as
         if the field is a repeated message field.
         NOTE: Do not set the option in .proto files. Always use the maps syntax
         instead. The option should only be implicitly set by the proto compiler
         parser.
         
        optional bool map_entry = 7;
        Specified by:
        getMapEntry in interface DescriptorProtos.MessageOptionsOrBuilder
        Returns:
        The mapEntry.
      • setMapEntry

        public DescriptorProtos.MessageOptions.Builder setMapEntry​(boolean value)
         Whether the message is an automatically generated map entry type for the
         maps field.
         For maps fields:
             map<KeyType, ValueType> map_field = 1;
         The parsed descriptor looks like:
             message MapFieldEntry {
                 option map_entry = true;
                 optional KeyType key = 1;
                 optional ValueType value = 2;
             }
             repeated MapFieldEntry map_field = 1;
         Implementations may choose not to generate the map_entry=true message, but
         use a native map in the target language to hold the keys and values.
         The reflection APIs in such implementations still need to work as
         if the field is a repeated message field.
         NOTE: Do not set the option in .proto files. Always use the maps syntax
         instead. The option should only be implicitly set by the proto compiler
         parser.
         
        optional bool map_entry = 7;
        Parameters:
        value - The mapEntry to set.
        Returns:
        This builder for chaining.
      • clearMapEntry

        public DescriptorProtos.MessageOptions.Builder clearMapEntry()
         Whether the message is an automatically generated map entry type for the
         maps field.
         For maps fields:
             map<KeyType, ValueType> map_field = 1;
         The parsed descriptor looks like:
             message MapFieldEntry {
                 option map_entry = true;
                 optional KeyType key = 1;
                 optional ValueType value = 2;
             }
             repeated MapFieldEntry map_field = 1;
         Implementations may choose not to generate the map_entry=true message, but
         use a native map in the target language to hold the keys and values.
         The reflection APIs in such implementations still need to work as
         if the field is a repeated message field.
         NOTE: Do not set the option in .proto files. Always use the maps syntax
         instead. The option should only be implicitly set by the proto compiler
         parser.
         
        optional bool map_entry = 7;
        Returns:
        This builder for chaining.
      • clearUninterpretedOption

        public DescriptorProtos.MessageOptions.Builder clearUninterpretedOption()
         The parser stores options it doesn't recognize here. See above.
         
        repeated .google.protobuf.UninterpretedOption uninterpreted_option = 999;
      • removeUninterpretedOption

        public DescriptorProtos.MessageOptions.Builder removeUninterpretedOption​(int index)
         The parser stores options it doesn't recognize here. See above.
         
        repeated .google.protobuf.UninterpretedOption uninterpreted_option = 999;
      • getUninterpretedOptionBuilder

        public DescriptorProtos.UninterpretedOption.Builder getUninterpretedOptionBuilder​(int index)
         The parser stores options it doesn't recognize here. See above.
         
        repeated .google.protobuf.UninterpretedOption uninterpreted_option = 999;
      • addUninterpretedOptionBuilder

        public DescriptorProtos.UninterpretedOption.Builder addUninterpretedOptionBuilder()
         The parser stores options it doesn't recognize here. See above.
         
        repeated .google.protobuf.UninterpretedOption uninterpreted_option = 999;
      • addUninterpretedOptionBuilder

        public DescriptorProtos.UninterpretedOption.Builder addUninterpretedOptionBuilder​(int index)
         The parser stores options it doesn't recognize here. See above.
         
        repeated .google.protobuf.UninterpretedOption uninterpreted_option = 999;
      • getUninterpretedOptionBuilderList

        public java.util.List<DescriptorProtos.UninterpretedOption.Builder> getUninterpretedOptionBuilderList()
         The parser stores options it doesn't recognize here. See above.
         
        repeated .google.protobuf.UninterpretedOption uninterpreted_option = 999;