Bug 139936 - [ltw] WeavingAdaptor.generatedClassesExist() cannot cope with additional class weaving
Summary: [ltw] WeavingAdaptor.generatedClassesExist() cannot cope with additional clas...
Status: RESOLVED FIXED
Alias: None
Product: AspectJ
Classification: Tools
Component: LTWeaving (show other bugs)
Version: DEVELOPMENT   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 1.5.2   Edit
Assignee: Matthew Webster CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-03 08:56 EDT by Matthew Webster CLA
Modified: 2006-06-19 08:49 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Matthew Webster CLA 2006-05-03 08:56:32 EDT 
If a closure is generate during LTW it is immediately defined to the JVM. The existing interface allows agents to determine whether a closure was generated. However when a class is defined additonal classes may be loaded, argument types used for the around advice for example, which may in turn be woven. The existing interface does not allow an agent to determine for which class a closure was generated.
Comment 1 Matthew Webster CLA 2006-06-15 10:47:33 EDT 
1. New ClassLoaderWeavingAdaptor.generatedClassesExistFor(String)
2. New JUnit tests for Aj and ClassLoaderWeavingAdaptor

Other enhancements for AOSGi
1. New IWeavingContext.getFile(URL) for formatting bundle URLs
2. New verbose "info not weaving" message
Comment 2 Andrew Clement CLA 2006-06-19 06:27:35 EDT 
is this resolved now?
Comment 3 Matthew Webster CLA 2006-06-19 08:49:32 EDT 
Fix available in aspectj-DEVELOPMENT-20060615180342.jar