com.google.protobuf

Class DescriptorProtos.MessageOptions.Builder

    • Method Detail

      • internalGetFieldAccessorTable

        protected GeneratedMessage.FieldAccessorTable internalGetFieldAccessorTable()
        Description copied from class: GeneratedMessage.Builder
        Get the FieldAccessorTable for this type. We can't have the message class pass this in to the constructor because of bootstrapping trouble with DescriptorProtos.

      • getDefaultInstanceForType

        public DescriptorProtos.MessageOptions getDefaultInstanceForType()
        Description copied from interface: MessageLiteOrBuilder
        Get an instance of the type with no fields set. Because no fields are set, all getters for singular fields will return default values and repeated fields will appear empty. This may or may not be a singleton. This differs from the getDefaultInstance() method of generated message classes in that this method is an abstract method of the MessageLite interface whereas getDefaultInstance() is a static method of a specific class. They return the same thing.

      • mergeFrom

        public DescriptorProtos.MessageOptions.Builder mergeFrom(Message other)
        Description copied from interface: Message.Builder
        Merge other into the message being built. other must have the exact same type as this (i.e. getDescriptorForType() == other.getDescriptorForType()). Merging occurs as follows. For each field:
        * For singular primitive fields, if the field is set in other, then other's value overwrites the value in this message.
        * For singular message fields, if the field is set in other, it is merged into the corresponding sub-message of this message using the same merging rules.
        * For repeated fields, the elements in other are concatenated with the elements in this message. This is equivalent to the Message::MergeFrom method in C++.

      • hasMessageSetWireFormat

        public boolean hasMessageSetWireFormat()
        optional bool message_set_wire_format = 1 [default = false]; 
         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.

      • getMessageSetWireFormat

        public boolean getMessageSetWireFormat()
        optional bool message_set_wire_format = 1 [default = false]; 
         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.

      • setMessageSetWireFormat

        public DescriptorProtos.MessageOptions.Builder setMessageSetWireFormat(boolean value)
        optional bool message_set_wire_format = 1 [default = false]; 
         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.

      • clearMessageSetWireFormat

        public DescriptorProtos.MessageOptions.Builder clearMessageSetWireFormat()
        optional bool message_set_wire_format = 1 [default = false]; 
         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.

      • hasNoStandardDescriptorAccessor

        public boolean hasNoStandardDescriptorAccessor()
        optional bool no_standard_descriptor_accessor = 2 [default = false]; 
         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".

      • getNoStandardDescriptorAccessor

        public boolean getNoStandardDescriptorAccessor()
        optional bool no_standard_descriptor_accessor = 2 [default = false]; 
         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".

      • setNoStandardDescriptorAccessor

        public DescriptorProtos.MessageOptions.Builder setNoStandardDescriptorAccessor(boolean value)
        optional bool no_standard_descriptor_accessor = 2 [default = false]; 
         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".

      • clearNoStandardDescriptorAccessor

        public DescriptorProtos.MessageOptions.Builder clearNoStandardDescriptorAccessor()
        optional bool no_standard_descriptor_accessor = 2 [default = false]; 
         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".

      • hasDeprecated

        public boolean hasDeprecated()
        optional bool deprecated = 3 [default = false]; 
         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.

      • getDeprecated

        public boolean getDeprecated()
        optional bool deprecated = 3 [default = false]; 
         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.

      • setDeprecated

        public DescriptorProtos.MessageOptions.Builder setDeprecated(boolean value)
        optional bool deprecated = 3 [default = false]; 
         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.

      • clearDeprecated

        public DescriptorProtos.MessageOptions.Builder clearDeprecated()
        optional bool deprecated = 3 [default = false]; 
         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.

      • getUninterpretedOptionList

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

      • getUninterpretedOptionCount

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

      • getUninterpretedOption

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

      • clearUninterpretedOption

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

      • removeUninterpretedOption

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

      • getUninterpretedOptionBuilder

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

      • getUninterpretedOptionOrBuilder

        public DescriptorProtos.UninterpretedOptionOrBuilder getUninterpretedOptionOrBuilder(int index)
        repeated .google.protobuf.UninterpretedOption uninterpreted_option = 999; 
         The parser stores options it doesn't recognize here. See above.

      • getUninterpretedOptionOrBuilderList

        public List<? extends DescriptorProtos.UninterpretedOptionOrBuilder> getUninterpretedOptionOrBuilderList()
        repeated .google.protobuf.UninterpretedOption uninterpreted_option = 999; 
         The parser stores options it doesn't recognize here. See above.

      • addUninterpretedOptionBuilder

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

      • addUninterpretedOptionBuilder

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

      • getUninterpretedOptionBuilderList

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