Bug 149140 - Use reflection to resolve non-bootstrap types during LTW
Summary: Use reflection to resolve non-bootstrap types during LTW
Status: NEW
Alias: None
Product: AspectJ
Classification: Tools
Component: LTWeaving (show other bugs)
Version: DEVELOPMENT   Edit
Hardware: PC Windows XP
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: aspectj inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-29 08:31 EDT by Matthew Webster CLA
Modified: 2007-10-24 11:15 EDT (History)
1 user (show)

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-06-29 08:31:44 EDT 
This is a post 1.5.2 refinement of Bug 114083 after then implementation of Bug 140695 "Use LTWWorld not BcelWorld for load-time weaving".

It should be possible to resolve non-bootstrap classes using reflection without needing weaver re-entrancy for non-locally defined classes. Simplistically one could use ClassLoader.getParent() for the application class loader (which was used to create the World) however this will break with non-delegating Java EE class loaders and have no benefit under OSGi (which had a different delegation model). One approach would be to use environment-specific IWeavingContext implementations which safely abstracted the delegation model.
Comment 1 Matthew Webster CLA 2006-09-25 06:24:36 EDT 
Won't make 1.5.3.