Help Center/ Object Storage Service/ SDK Reference/ Java/ Before You Start (SDK for Java)

Updated on 2024-06-18 GMT+08:00

View PDF

Before You Start (SDK for Java)

This section describes version updates and compatibility and important notes about Object Storage Service (OBS) SDK for Java.

Version Updates

Table 1 describes the version updates and compatibility of OBS SDK for Java.

**Table 1** Version updates and compatibility of OBS SDK for Java
Version	Update	Description	Compatible or Not
v3.23.9.1	New features Adaptation to third-party dependencies	New features: Allowed you to customize DNS resolvers. Adaptation to third-party dependencies: Removed java-xmlbuilder and used the default javax.xml library.	-
v3.23.9	New features Adaptation to third-party dependencies	New features: Added the API for configuring bucket inventories. Added client-side encryption. Allowed you to configure the expiration time of fragments in lifecycle rules. Adaptation to third-party dependencies: Replaced Okio 2.10.0 with Okio 3.5.0. Replaced OkHttp 4.10.0 with OkHttp 4.11.0.	Yes
v3.23.5	New features	New features: Added the dual-write feature to buckets. Supported the Standard, Infrequent Access, and Archive storage classes. Supported capacity statistics on storage in three storage classes.	Yes
v3.23.3	New features Adaptation to third-party dependencies	New features: Allowed you to query the progress of cross-region replication. Added the APIs for setting, obtaining, and deleting object tags. Adaptation to third-party dependencies: Replaced powermock-module-junit4 1.6.5 with powermock-module-junit4 2.0.9. Replaced powermock-api-mockito 1.6.5 with powermock-api-mockito2 2.0.9. Replaced mockito-core 1.10.19 with mockito-core 4.11.0.	Yes
v3.22.12	New features Adaptation to third-party dependencies	New features: Added the posix-accessible APIs. Adaptation to third-party dependencies: Replaced log4j2 2.17.1 with log4j2 2.18.0. Replaced okhttp 4.9.3 with okhttp 4.10.0. Replaced jackson-core 2.13.0 with jackson-core 2.13.3. Replaced jackson-databind 2.13.0 with jackson-databind 2.13.4.1. Replaced jackson-annotations 2.13.0 with jackson-annotations 2.13.3.	Yes
v3.22.3	Adaptation to third-party dependencies	Replaced log4j2 2.17.0 with log4j2 2.17.1. Replaced okhttp 4.9.1 with okhttp 4.9.3. Replaced Okio 2.7.0 with Okio 2.10.0. Replaced jackson-core 2.12.5 with jackson-core 2.13.0. Replaced jackson-databind 2.12.5 with jackson-databind 2.13.0. Replaced jackson-annotations 2.12.5 with jackson-annotations 2.13.0.	Yes
v3.21.12	Adaptation to third-party dependencies	Replaced log4j2 2.16.0 with log4j2 2.17.0.	Yes
v3.21.11	New features Adaptation to third-party dependencies	New features: Allowed you to add user-defined headers in the requests. Adaptation to third-party dependencies: Replaced jackson-core 2.11.1 with jackson-core 2.12.5. Replaced jackson-databind 2.11.1 with jackson-databind 2.12.5. Replaced jackson-annotations 2.11.1 with jackson-annotations 2.12.5. Replaced OkHttp 4.8.0 with OkHttp 4.9.1. Replaced log4j2 2.14.1 with log4j2 2.16.0.	Yes

For more information about version updates, see ChangeLog.

Compatibility

Recommended JDK versions: JDK 8 or later
The earlier 2.X versions are no longer maintained. You are advised to upgrade them to the latest version as soon as possible.

Important Notes

To make the most of this document, download the latest version of Java SDK from SDK Download and Installation (SDK for Java).
Make sure that you are familiar with basic OBS concepts, such as buckets, objects, access keys (AKs/SKs), and endpoints and domain names.
You can learn about how to call an API through the OBS SDK for Java by referring to Using an OBS Client.
After an API is called using an instance of ObsClient, if no exception is thrown, the return value is valid. If an exception is thrown, the operation fails. For details about errors, see SDK Exceptions (SDK for Java).
After any API is called using an instance of ObsClient, common response headers including their subheaders will be returned.
Some features are available only in some regions. If an API call returns the 405 HTTP status code, check whether the region supports this feature. For details, refer to Function Overview or submit a service ticket to contact technical support.