Bug 30794

Summary:

Minor API changes to support weaving classloader implementation

Product:

[Tools] AspectJ

Reporter:

Martin Lippert <mlippert>

Component:

Compiler

Assignee:

Jim Hugunin <jim-aj>

Status:

RESOLVED FIXED

QA Contact:

Severity:

normal

Priority:

CC:

aclement

Version:

unspecified

Target Milestone:

---

Hardware:

OS:

Windows 2000

Whiteboard:

Attachments:

Description	Flags
patch file for weaver project	aclement: iplog+

Description Martin Lippert

2003-02-03 02:05:00 EST

I've implemented a classloader which does the weaving at the bytecode level at
class loading time. Therefore I used the weaving functionality implemented in
the weaver project of AspectJ. To implement the classloader I made some minor
API changes (mostly setting a method from private or package to public) and
added a few methods. I would be great if the changes could be integrated into
the head AspectJ project.

One method I added to BcelWeaver is still non-optimal. The new method
"weaveWithoutDump" contains a lot of duplicated code from the "weave" method
(with the same parameters). I will refactor this in the near future.

Thanks!!!
-Martin

Comment 1 Martin Lippert

2003-02-03 02:22:24 EST

Created attachment 3264 [details]
patch file for weaver project

Comment 2 Jim Hugunin

2003-02-13 21:01:05 EST

applied patch with no issues.  Made some internal modifications to avoid 
duplicating code in weave method, but left the public weaveWithoutDump method 
in place at least for now.