Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Add Spring Boot auto-configuration for standalone ActivityClient

Aberta
  • Algo errado?
#3,146 2 comentários 0 reações 1 responsável Ver no GitHub

Mantenedores costumam responder em até 2 dias

@Quinn-With-Two-Ns já está trabalhando nisso.

Desde 23/10/2026.

  • #3157 de @Quinn-With-Two-Ns — aberto

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
35/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
java, spring-boot
Domínio
backend

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Java
Estrelas
441
Forks
260
Merge médio
5d 3h
PRs com merge (30d)
19

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de temporalio/sdk-java

Todas as issues de temporalio/sdk-java

Issues semelhantes

Mais issues de Java

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.