Jul 30, 2025

Tomer Aberbach

Although the generated Java/Kotlin SDKs use reflection, they can be made usable in GraalVM by publishing them with reachability metadata. This can be enabled by setting targets.{java,kotlin}.publish.graalvm_metadata to true.

GraalVM should automatically detect and use the published metadata, but manual configuration is also available for end-users.

Jul 30, 2025

Tomer Aberbach

Although the generated Java/Kotlin SDKs use reflection, they can be made usable in GraalVM by publishing them with reachability metadata. This can be enabled by setting targets.{java,kotlin}.publish.graalvm_metadata to true.

GraalVM should automatically detect and use the published metadata, but manual configuration is also available for end-users.

Jul 30, 2025

Tomer Aberbach

Although the generated Java/Kotlin SDKs use reflection, they can be made usable in GraalVM by publishing them with reachability metadata. This can be enabled by setting targets.{java,kotlin}.publish.graalvm_metadata to true.

GraalVM should automatically detect and use the published metadata, but manual configuration is also available for end-users.

Jul 30, 2025

Tomer Aberbach

The generated Java/Kotlin SDKs can now include an automatically generated Spring Boot starter package to simplify configuration for users who use Spring Boot.

This can be enabled by setting targets.{java,kotlin}.publish.spring_boot_starter to true in the Stainless config.

Jul 30, 2025

Tomer Aberbach

The generated Java/Kotlin SDKs can now include an automatically generated Spring Boot starter package to simplify configuration for users who use Spring Boot.

This can be enabled by setting targets.{java,kotlin}.publish.spring_boot_starter to true in the Stainless config.

Jul 30, 2025

Tomer Aberbach

The generated Java/Kotlin SDKs can now include an automatically generated Spring Boot starter package to simplify configuration for users who use Spring Boot.

This can be enabled by setting targets.{java,kotlin}.publish.spring_boot_starter to true in the Stainless config.

Jun 30, 2025

Tomer Aberbach

The Java and Kotlin SDKs now support server variables in base URLs. If your OpenAPI spec includes templated URLs like https://{username}.example.com:{port}/{basePath}, the generated SDK will expose configuration options to fill in {username}, {port}, or {basePath}.

Jun 30, 2025

Tomer Aberbach

The Java and Kotlin SDKs now support server variables in base URLs. If your OpenAPI spec includes templated URLs like https://{username}.example.com:{port}/{basePath}, the generated SDK will expose configuration options to fill in {username}, {port}, or {basePath}.

Jun 30, 2025

Tomer Aberbach

The Java and Kotlin SDKs now support server variables in base URLs. If your OpenAPI spec includes templated URLs like https://{username}.example.com:{port}/{basePath}, the generated SDK will expose configuration options to fill in {username}, {port}, or {basePath}.

Jun 2, 2025

Tomer Aberbach

The Java/Kotlin SDKs now support configuring a query param as the discriminator for a method that supports both streaming and non-streaming.

When configured this way the HTTP method will result int two generated SDK methods. For example, an HTTP method called create will result in the following two SDK methods:

  • create → doesn’t send the query param discriminator

  • createStreaming → sends the query param discriminator set to true

To configure SSE streaming for your API, send us a note.

Jun 2, 2025

Tomer Aberbach

The Java/Kotlin SDKs now support configuring a query param as the discriminator for a method that supports both streaming and non-streaming.

When configured this way the HTTP method will result int two generated SDK methods. For example, an HTTP method called create will result in the following two SDK methods:

  • create → doesn’t send the query param discriminator

  • createStreaming → sends the query param discriminator set to true

To configure SSE streaming for your API, send us a note.

Jun 2, 2025

Tomer Aberbach

The Java/Kotlin SDKs now support configuring a query param as the discriminator for a method that supports both streaming and non-streaming.

When configured this way the HTTP method will result int two generated SDK methods. For example, an HTTP method called create will result in the following two SDK methods:

  • create → doesn’t send the query param discriminator

  • createStreaming → sends the query param discriminator set to true

To configure SSE streaming for your API, send us a note.