spring-projects / spring-projects/spring-framework
Load-time weaving not applying to beans defined by Configuration classes [SPR-9215]
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 60.2k
- Forks
- 38.8k
- Avg merge
- 5d 2h
- Merged PRs (30d)
- 27
Description
Noodle opened SPR-9215 and commented
When use Java Configuration, aspectj weaver cannot see spring beans with @Component, @Service @Repository annotations.
Affects: 3.1 GA
Reference URL: http://forum.springsource.org/showthread.php?124055-XML-vs-Java-Config-for-aspectj-transaction
Referenced from: commits https://github.com/spring-projects/spring-framework-issues/commit/55ed933a53d007662883bf8a63c27570165507ef, https://github.com/spring-projects/spring-framework-issues/commit/8a412ec9fa1ef7de87a7ec697fc80cc56c466077
7 votes, 13 watchers
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 reviewing the issue's Java Configuration and load-time-weaving context, along with the referenced commits and forum discussion. Reproduce the reported case with @Component, @Service, or @Repository beans, then verify that beans defined through Configuration classes are visible to the AspectJ weaver without regressing existing XML-based behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100