spring-cloud / spring-cloud/spring-cloud-zookeeper
CuratorFrameworkCustomizer can't be injected when "spring-cloud-starter-zookeeper-config" on the classpath
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 574
- Forks
- 408
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 4
Description
SpringBoot: 2.3.0.Release
SpringCloud: Hoxton.SR5
I want to config CuratorFramework by declaring CuratorFrameworkCustomizer as a bean. if only "spring-cloud-starter-zookeeper-discovery" on the classpath, CuratorFrameworkCustomizer can be injected into "ZooKeeperAutoConfiguration". But if I use "spring-cloud-starter-zookeeper-config" at the same time OR only use "spring-cloud-starter-zookeeper-config", it doesn't works. CuratorFrameworkCustomizer can't be injected.
I watched that "ZooKeeperAutoConfiguration" was loaded in different order.
Contributor guide
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 by reproducing the issue with spring-cloud-starter-zookeeper-discovery and spring-cloud-starter-zookeeper-config, then inspect ZooKeeperAutoConfiguration and CuratorFrameworkCustomizer injection ordering. Done means a declared CuratorFrameworkCustomizer bean can be injected in both classpath combinations described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100