Package akka.protobuf

Class DescriptorProtos.FileOptions.Builder

    • Method Detail

      • getDefaultInstanceForType

        public DescriptorProtos.FileOptions 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.
        Specified by:
        getDefaultInstanceForType in interface MessageLiteOrBuilder
        Specified by:
        getDefaultInstanceForType in interface MessageOrBuilder

      • mergeFrom

        public DescriptorProtos.FileOptions.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++.
        Specified by:
        mergeFrom in interface Message.Builder
        Overrides:
        mergeFrom in class AbstractMessage.Builder<DescriptorProtos.FileOptions.Builder>

      • hasJavaPackage

        public boolean hasJavaPackage()
        optional string java_package = 1; 
         Sets the Java package where classes generated from this .proto will be
 placed.  By default, the proto package is used, but this is often
 inappropriate because proto packages do not normally start with backwards
 domain names.
        Specified by:
        hasJavaPackage in interface DescriptorProtos.FileOptionsOrBuilder

      • getJavaPackage

        public java.lang.String getJavaPackage()
        optional string java_package = 1; 
         Sets the Java package where classes generated from this .proto will be
 placed.  By default, the proto package is used, but this is often
 inappropriate because proto packages do not normally start with backwards
 domain names.
        Specified by:
        getJavaPackage in interface DescriptorProtos.FileOptionsOrBuilder

      • getJavaPackageBytes

        public ByteString getJavaPackageBytes()
        optional string java_package = 1; 
         Sets the Java package where classes generated from this .proto will be
 placed.  By default, the proto package is used, but this is often
 inappropriate because proto packages do not normally start with backwards
 domain names.
        Specified by:
        getJavaPackageBytes in interface DescriptorProtos.FileOptionsOrBuilder

      • setJavaPackage

        public DescriptorProtos.FileOptions.Builder setJavaPackage​(java.lang.String value)
        optional string java_package = 1; 
         Sets the Java package where classes generated from this .proto will be
 placed.  By default, the proto package is used, but this is often
 inappropriate because proto packages do not normally start with backwards
 domain names.

      • clearJavaPackage

        public DescriptorProtos.FileOptions.Builder clearJavaPackage()
        optional string java_package = 1; 
         Sets the Java package where classes generated from this .proto will be
 placed.  By default, the proto package is used, but this is often
 inappropriate because proto packages do not normally start with backwards
 domain names.

      • setJavaPackageBytes

        public DescriptorProtos.FileOptions.Builder setJavaPackageBytes​(ByteString value)
        optional string java_package = 1; 
         Sets the Java package where classes generated from this .proto will be
 placed.  By default, the proto package is used, but this is often
 inappropriate because proto packages do not normally start with backwards
 domain names.

      • hasJavaOuterClassname

        public boolean hasJavaOuterClassname()
        optional string java_outer_classname = 8; 
         If set, all the classes from the .proto file are wrapped in a single
 outer class with the given name.  This applies to both Proto1
 (equivalent to the old "--one_java_file" option) and Proto2 (where
 a .proto always translates to a single class, but you may want to
 explicitly choose the class name).
        Specified by:
        hasJavaOuterClassname in interface DescriptorProtos.FileOptionsOrBuilder

      • getJavaOuterClassname

        public java.lang.String getJavaOuterClassname()
        optional string java_outer_classname = 8; 
         If set, all the classes from the .proto file are wrapped in a single
 outer class with the given name.  This applies to both Proto1
 (equivalent to the old "--one_java_file" option) and Proto2 (where
 a .proto always translates to a single class, but you may want to
 explicitly choose the class name).
        Specified by:
        getJavaOuterClassname in interface DescriptorProtos.FileOptionsOrBuilder

      • getJavaOuterClassnameBytes

        public ByteString getJavaOuterClassnameBytes()
        optional string java_outer_classname = 8; 
         If set, all the classes from the .proto file are wrapped in a single
 outer class with the given name.  This applies to both Proto1
 (equivalent to the old "--one_java_file" option) and Proto2 (where
 a .proto always translates to a single class, but you may want to
 explicitly choose the class name).
        Specified by:
        getJavaOuterClassnameBytes in interface DescriptorProtos.FileOptionsOrBuilder

      • setJavaOuterClassname

        public DescriptorProtos.FileOptions.Builder setJavaOuterClassname​(java.lang.String value)
        optional string java_outer_classname = 8; 
         If set, all the classes from the .proto file are wrapped in a single
 outer class with the given name.  This applies to both Proto1
 (equivalent to the old "--one_java_file" option) and Proto2 (where
 a .proto always translates to a single class, but you may want to
 explicitly choose the class name).

      • clearJavaOuterClassname

        public DescriptorProtos.FileOptions.Builder clearJavaOuterClassname()
        optional string java_outer_classname = 8; 
         If set, all the classes from the .proto file are wrapped in a single
 outer class with the given name.  This applies to both Proto1
 (equivalent to the old "--one_java_file" option) and Proto2 (where
 a .proto always translates to a single class, but you may want to
 explicitly choose the class name).

      • setJavaOuterClassnameBytes

        public DescriptorProtos.FileOptions.Builder setJavaOuterClassnameBytes​(ByteString value)
        optional string java_outer_classname = 8; 
         If set, all the classes from the .proto file are wrapped in a single
 outer class with the given name.  This applies to both Proto1
 (equivalent to the old "--one_java_file" option) and Proto2 (where
 a .proto always translates to a single class, but you may want to
 explicitly choose the class name).

      • hasJavaMultipleFiles

        public boolean hasJavaMultipleFiles()
        optional bool java_multiple_files = 10 [default = false]; 
         If set true, then the Java code generator will generate a separate .java
 file for each top-level message, enum, and service defined in the .proto
 file.  Thus, these types will *not* be nested inside the outer class
 named by java_outer_classname.  However, the outer class will still be
 generated to contain the file's getDescriptor() method as well as any
 top-level extensions defined in the file.
        Specified by:
        hasJavaMultipleFiles in interface DescriptorProtos.FileOptionsOrBuilder

      • getJavaMultipleFiles

        public boolean getJavaMultipleFiles()
        optional bool java_multiple_files = 10 [default = false]; 
         If set true, then the Java code generator will generate a separate .java
 file for each top-level message, enum, and service defined in the .proto
 file.  Thus, these types will *not* be nested inside the outer class
 named by java_outer_classname.  However, the outer class will still be
 generated to contain the file's getDescriptor() method as well as any
 top-level extensions defined in the file.
        Specified by:
        getJavaMultipleFiles in interface DescriptorProtos.FileOptionsOrBuilder

      • setJavaMultipleFiles

        public DescriptorProtos.FileOptions.Builder setJavaMultipleFiles​(boolean value)
        optional bool java_multiple_files = 10 [default = false]; 
         If set true, then the Java code generator will generate a separate .java
 file for each top-level message, enum, and service defined in the .proto
 file.  Thus, these types will *not* be nested inside the outer class
 named by java_outer_classname.  However, the outer class will still be
 generated to contain the file's getDescriptor() method as well as any
 top-level extensions defined in the file.

      • clearJavaMultipleFiles

        public DescriptorProtos.FileOptions.Builder clearJavaMultipleFiles()
        optional bool java_multiple_files = 10 [default = false]; 
         If set true, then the Java code generator will generate a separate .java
 file for each top-level message, enum, and service defined in the .proto
 file.  Thus, these types will *not* be nested inside the outer class
 named by java_outer_classname.  However, the outer class will still be
 generated to contain the file's getDescriptor() method as well as any
 top-level extensions defined in the file.

      • hasJavaGenerateEqualsAndHash

        public boolean hasJavaGenerateEqualsAndHash()
        optional bool java_generate_equals_and_hash = 20 [default = false]; 
         If set true, then the Java code generator will generate equals() and
 hashCode() methods for all messages defined in the .proto file. This is
 purely a speed optimization, as the AbstractMessage base class includes
 reflection-based implementations of these methods.
        Specified by:
        hasJavaGenerateEqualsAndHash in interface DescriptorProtos.FileOptionsOrBuilder

      • getJavaGenerateEqualsAndHash

        public boolean getJavaGenerateEqualsAndHash()
        optional bool java_generate_equals_and_hash = 20 [default = false]; 
         If set true, then the Java code generator will generate equals() and
 hashCode() methods for all messages defined in the .proto file. This is
 purely a speed optimization, as the AbstractMessage base class includes
 reflection-based implementations of these methods.
        Specified by:
        getJavaGenerateEqualsAndHash in interface DescriptorProtos.FileOptionsOrBuilder

      • setJavaGenerateEqualsAndHash

        public DescriptorProtos.FileOptions.Builder setJavaGenerateEqualsAndHash​(boolean value)
        optional bool java_generate_equals_and_hash = 20 [default = false]; 
         If set true, then the Java code generator will generate equals() and
 hashCode() methods for all messages defined in the .proto file. This is
 purely a speed optimization, as the AbstractMessage base class includes
 reflection-based implementations of these methods.

      • clearJavaGenerateEqualsAndHash

        public DescriptorProtos.FileOptions.Builder clearJavaGenerateEqualsAndHash()
        optional bool java_generate_equals_and_hash = 20 [default = false]; 
         If set true, then the Java code generator will generate equals() and
 hashCode() methods for all messages defined in the .proto file. This is
 purely a speed optimization, as the AbstractMessage base class includes
 reflection-based implementations of these methods.

      • hasGoPackage

        public boolean hasGoPackage()
        optional string go_package = 11; 
         Sets the Go package where structs generated from this .proto will be
 placed.  There is no default.
        Specified by:
        hasGoPackage in interface DescriptorProtos.FileOptionsOrBuilder

      • getGoPackage

        public java.lang.String getGoPackage()
        optional string go_package = 11; 
         Sets the Go package where structs generated from this .proto will be
 placed.  There is no default.
        Specified by:
        getGoPackage in interface DescriptorProtos.FileOptionsOrBuilder

      • setGoPackage

        public DescriptorProtos.FileOptions.Builder setGoPackage​(java.lang.String value)
        optional string go_package = 11; 
         Sets the Go package where structs generated from this .proto will be
 placed.  There is no default.

      • clearGoPackage

        public DescriptorProtos.FileOptions.Builder clearGoPackage()
        optional string go_package = 11; 
         Sets the Go package where structs generated from this .proto will be
 placed.  There is no default.

      • setGoPackageBytes

        public DescriptorProtos.FileOptions.Builder setGoPackageBytes​(ByteString value)
        optional string go_package = 11; 
         Sets the Go package where structs generated from this .proto will be
 placed.  There is no default.

      • hasCcGenericServices

        public boolean hasCcGenericServices()
        optional bool cc_generic_services = 16 [default = false]; 
         Should generic services be generated in each language?  "Generic" services
 are not specific to any particular RPC system.  They are generated by the
 main code generators in each language (without additional plugins).
 Generic services were the only kind of service generation supported by
 early versions of proto2.

 Generic services are now considered deprecated in favor of using plugins
 that generate code specific to your particular RPC system.  Therefore,
 these default to false.  Old code which depends on generic services should
 explicitly set them to true.
        Specified by:
        hasCcGenericServices in interface DescriptorProtos.FileOptionsOrBuilder

      • getCcGenericServices

        public boolean getCcGenericServices()
        optional bool cc_generic_services = 16 [default = false]; 
         Should generic services be generated in each language?  "Generic" services
 are not specific to any particular RPC system.  They are generated by the
 main code generators in each language (without additional plugins).
 Generic services were the only kind of service generation supported by
 early versions of proto2.

 Generic services are now considered deprecated in favor of using plugins
 that generate code specific to your particular RPC system.  Therefore,
 these default to false.  Old code which depends on generic services should
 explicitly set them to true.
        Specified by:
        getCcGenericServices in interface DescriptorProtos.FileOptionsOrBuilder

      • setCcGenericServices

        public DescriptorProtos.FileOptions.Builder setCcGenericServices​(boolean value)
        optional bool cc_generic_services = 16 [default = false]; 
         Should generic services be generated in each language?  "Generic" services
 are not specific to any particular RPC system.  They are generated by the
 main code generators in each language (without additional plugins).
 Generic services were the only kind of service generation supported by
 early versions of proto2.

 Generic services are now considered deprecated in favor of using plugins
 that generate code specific to your particular RPC system.  Therefore,
 these default to false.  Old code which depends on generic services should
 explicitly set them to true.

      • clearCcGenericServices

        public DescriptorProtos.FileOptions.Builder clearCcGenericServices()
        optional bool cc_generic_services = 16 [default = false]; 
         Should generic services be generated in each language?  "Generic" services
 are not specific to any particular RPC system.  They are generated by the
 main code generators in each language (without additional plugins).
 Generic services were the only kind of service generation supported by
 early versions of proto2.

 Generic services are now considered deprecated in favor of using plugins
 that generate code specific to your particular RPC system.  Therefore,
 these default to false.  Old code which depends on generic services should
 explicitly set them to true.

      • clearUninterpretedOption

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

      • removeUninterpretedOption

        public DescriptorProtos.FileOptions.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.

      • 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 java.util.List<DescriptorProtos.UninterpretedOption.Builder> getUninterpretedOptionBuilderList()
        repeated .google.protobuf.UninterpretedOption uninterpreted_option = 999; 
         The parser stores options it doesn't recognize here. See above.