Reference documentation and code samples for the Private Catalog V1beta1 API class Google::Api::JavaSettings.
Settings for Java client libraries.
Inherits
- Object
Extended By
- Google::Protobuf::MessageExts::ClassMethods
Includes
- Google::Protobuf::MessageExts
Methods
#common
def common() -> ::Google::Api::CommonLanguageSettings
- (::Google::Api::CommonLanguageSettings) — Some settings.
#common=
def common=(value) -> ::Google::Api::CommonLanguageSettings
- value (::Google::Api::CommonLanguageSettings) — Some settings.
- (::Google::Api::CommonLanguageSettings) — Some settings.
#library_package
def library_package() -> ::String
-
(::String) — The package name to use in Java. Clobbers the java_package option
set in the protobuf. This should be used only by APIs
who have already set the language_settings.java.package_name" field
in gapic.yaml. API teams should use the protobuf java_package option
where possible.
Example of a YAML configuration::
publishing: java_settings: library_package: com.google.cloud.pubsub.v1
#library_package=
def library_package=(value) -> ::String
-
value (::String) — The package name to use in Java. Clobbers the java_package option
set in the protobuf. This should be used only by APIs
who have already set the language_settings.java.package_name" field
in gapic.yaml. API teams should use the protobuf java_package option
where possible.
Example of a YAML configuration::
publishing: java_settings: library_package: com.google.cloud.pubsub.v1
-
(::String) — The package name to use in Java. Clobbers the java_package option
set in the protobuf. This should be used only by APIs
who have already set the language_settings.java.package_name" field
in gapic.yaml. API teams should use the protobuf java_package option
where possible.
Example of a YAML configuration::
publishing: java_settings: library_package: com.google.cloud.pubsub.v1
#service_class_names
def service_class_names() -> ::Google::Protobuf::Map{::String => ::String}
-
(::Google::Protobuf::Map{::String => ::String}) — Configure the Java class name to use instead of the service's for its
corresponding generated GAPIC client. Keys are fully-qualified
service names as they appear in the protobuf (including the full
the language_settings.java.interface_names" field in gapic.yaml. API
teams should otherwise use the service name as it appears in the
protobuf.
Example of a YAML configuration::
publishing: java_settings: service_class_names: - google.pubsub.v1.Publisher: TopicAdmin - google.pubsub.v1.Subscriber: SubscriptionAdmin
#service_class_names=
def service_class_names=(value) -> ::Google::Protobuf::Map{::String => ::String}
-
value (::Google::Protobuf::Map{::String => ::String}) — Configure the Java class name to use instead of the service's for its
corresponding generated GAPIC client. Keys are fully-qualified
service names as they appear in the protobuf (including the full
the language_settings.java.interface_names" field in gapic.yaml. API
teams should otherwise use the service name as it appears in the
protobuf.
Example of a YAML configuration::
publishing: java_settings: service_class_names: - google.pubsub.v1.Publisher: TopicAdmin - google.pubsub.v1.Subscriber: SubscriptionAdmin
-
(::Google::Protobuf::Map{::String => ::String}) — Configure the Java class name to use instead of the service's for its
corresponding generated GAPIC client. Keys are fully-qualified
service names as they appear in the protobuf (including the full
the language_settings.java.interface_names" field in gapic.yaml. API
teams should otherwise use the service name as it appears in the
protobuf.
Example of a YAML configuration::
publishing: java_settings: service_class_names: - google.pubsub.v1.Publisher: TopicAdmin - google.pubsub.v1.Subscriber: SubscriptionAdmin