KafkaStreamsExtendedBindingProperties is JDK proxy while resolving to create for kafkaStreamsFunctionProcessor in KafkaStreamsBinderSupportAutoConfiguration

Open
#3,144 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
java, kafka, spring
Domain
backend, stream-processing

Research direction

Start with KafkaStreamsBinderSupportAutoConfiguration.kafkaStreamsFunctionProcessor at the linked line and reproduce the reported error with spring-cloud-stream 4.2.0 on Java 21. Review the changes referenced in issues 2974 and 3071 to determine why KafkaStreamsExtendedBindingProperties resolves as a JDK proxy. Done means the processor resolves the expected concrete binding-properties type without the reported dependency error.

Written by the indexing model from the issue text.

Description

KafkaStreamsBinderSupportAutoConfiguration.kafkaStreamsFunctionProcessor

encounteres

Unsatisfied dependency expressed through method 'kafkaStreamsFunctionProcessor' parameter 1: Bean named 'spring.cloud.stream.kafka.streams-org.springframework.cloud.stream.binder.kafka.streams.properties.KafkaStreamsExtendedBindingProperties' is expected to be of type 'org.springframework.cloud.stream.binder.kafka.streams.properties.KafkaStreamsExtendedBindingProperties' but was actually of type 'jdk.proxy2.$Proxy456'

most probably due to changes done here https://github.com/spring-cloud/spring-cloud-stream/issues/2974 (@olegz ) and discussed here https://github.com/spring-cloud/spring-cloud-stream/issues/3071

spring-cloud-stream 4.2.0
java 21

Dominant language
Java
Stars
1.1k
Forks
646
Avg merge
2d 3h
Merged PRs (30d)
8

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from spring-cloud/spring-cloud-stream

All issues in spring-cloud/spring-cloud-stream

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.