spring-cloud / spring-cloud/spring-cloud-stream
KafkaStreamsExtendedBindingProperties is JDK proxy while resolving to create for kafkaStreamsFunctionProcessor in KafkaStreamsBinderSupportAutoConfiguration
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 646
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 8
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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Tech stack
- java, kafka, spring
- Domain
- backend, stream-processing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100