Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Add Spring Boot auto-configuration for standalone ActivityClient

Aperta
  • Qualcosa non va?
#3,146 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@Quinn-With-Two-Ns ci sta già lavorando.

Dal 20/10/2026.

  • #3157 di @Quinn-With-Two-Ns — aperta

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
java, spring-boot
Ambito
backend

Direzione di ricerca

The issue names no files. Start from the existing WorkflowClient and ScheduleClient auto-configuration in the Spring Boot integration and copy its bean naming, @Primary handling, and backoff conditions for ActivityClient. Done means a root ActivityClient injects without a qualifier, non-root clients resolve by alias, and tests cover customizers and application-provided clients.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

What would you like added?

The Java SDK provides ActivityClient for starting and managing standalone activity executions, but the Temporal Spring Boot integration does not currently auto-configure it.

Please add ActivityClient support alongside the existing WorkflowClient and ScheduleClient support, including root and non-root namespaces.

Why is this needed?

Currently, applications must declare their own ActivityClient beans and manually apply namespace, data converter, and interceptor configuration.

Auto-configuration would make standalone activities easier to use from controllers and other Spring-managed components, while keeping client configuration consistent with the rest of the Temporal integration.

Proposed behavior

1. Register a client for each configured namespace.

Follow the existing client bean naming conventions:

  • Root namespace: temporalActivityClient, marked @Primary.
  • Non-root namespace: <namespace-alias>ActivityClient, falling back to the namespace name when no alias is configured.

For example:

spring:
  temporal:
    namespace: apps

    namespaces:
      - namespace: partner
        alias: partner

Applications could then inject the root client:

public AppsController(ActivityClient activityClient) {
  this.activityClient = activityClient;
}

Or select a non-root client:

public PartnerController(
    @Qualifier("partnerActivityClient") ActivityClient activityClient) {
  this.activityClient = activityClient;
}

2. Apply namespace-specific configuration.

Each client should use the appropriate:

  • WorkflowServiceStubs and connection configuration.
  • Namespace.
  • Data converter.
  • Activity client interceptors.

Provide an options customization hook consistent with the existing integration:

@Bean
public TemporalOptionsCustomizer<ActivityClientOptions.Builder>
    activityClientCustomizer() {
  return builder -> builder.setIdentity("my-application");
}

Support namespace-specific customizers using the existing non-root customization conventions.

3. Keep operation options at the invocation level.

StartActivityOptions, including task queue and timeouts, should remain arguments to activity invocations rather than become part of the auto-configured client.

4. Support application-provided clients.

Follow the integration’s bean override/backoff conventions so applications can supply their own client without conflicting with auto-configuration.

Acceptance criteria
  • Root ActivityClient can be injected without a qualifier.
  • Non-root clients can be selected by namespace/alias qualifier.
  • Namespace-specific connections, converters, interceptors, and options customizers are applied correctly.
  • Tests cover root and multiple non-root namespaces, customization, and application-provided clients.
  • Documentation includes configuration, injection, and a standalone activity invocation example.
Breaking changes?

None intended. This adds Spring-managed clients for an existing SDK API.

Server PR

No additional server changes are expected for the Spring integration itself.

Lingua principale
Java
Stelle
437
Fork
261
Merge medio
4g 9h
PR unite (30g)
20

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di temporalio/sdk-java

Tutte le issue di temporalio/sdk-java

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.