spring-projects / spring-projects/spring-framework
Reliably apply AspectJ weaving to @Component classes with LoadTimeWeaver setup on Tomcat
Open
Nobody has claimed this yet.
in: core
type: enhancement
- Dominant language
- Java
- Stars
- 60.2k
- Forks
- 38.8k
- Avg merge
- 5d 2h
- Merged PRs (30d)
- 27
Description
Affects: 6.0.2
We are trying to migrate from 5.3.19 to 6.0.2 and it seems that @Service beans and @Component beans are not woven anymore.
In our case, the result is that our @Transactionnal methods are no longer advised by the AnnotationTransactionAspect.
Looks like the issue was already present in older spring version.
I use the -javaagent:aspectjweaver.jar as a workaround but it is clearly not ideal for our project.
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
The report names no source file or test entry point. Start by reproducing the migration from Spring 5.3.19 to 6.0.2 with LoadTimeWeaver on Tomcat, then compare it with the -javaagent:aspectjweaver.jar workaround. Done means @Service and @Component beans are reliably woven and their @Transactional methods are advised without that workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100