spring-projects / spring-projects/spring-framework
upgrading spring naming policy for CGLIB proxies
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 60.2k
- Forks
- 38.8k
- Avg merge
- 5d 2h
- Merged PRs (30d)
- 27
Description
the current behavior of spring naming policy for CGLIB proxies is like this <beanName>$$SpringCGLIB$$N where N is the first available namespace . this is working very well in JVM but breaks in native image because proxies are be loaded from classpath instead for dynamically generated and if 2 proxies for bthe same bean are loaded spring will end up looking for both of them in $$0 creating issue #30985 .
proposal :
since we can not have 2 proxies for the same bean at the same operation level , instead of $$N representing the first available namespace it will represent the operating level of the proxy (0=aop, 1 = lazy, 2 =scope ,3= configs ...so on).
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 locating Spring's current naming policy for CGLIB proxies and read issue #30985 for the native-image failure context. Determine how proxy operating levels are represented and validated; done means a decided naming policy that avoids collisions for proxies of the same bean and has coverage for the affected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100