Re: [aspectwerkz-user] Applying aspects to Eclipse

Hi

Our load time weaving does intercept any classloader, and it has been
reported to work fine with OSGi bundles that Eclipse is using.
May be the "verbose" options from the FAQ will help to have some information.

from FAQ:
 What are the common steps to perform when I have some troubles?
    The following options and process are common answers to problems:

        * use -Daspectwerkz.transform.verbose=true (or -verbose with
offline mode command line tool and Ant task) to turn on the verbose
mode that will tell more when classes gets presented to the weaver.
        * use -Daspectwerkz.transform.details=true (or -details with
offline mode command line tool and Ant task) to turn on pointcut
matching verbose mode that will tell more when pointcuts match. This
is usefull to understand why "nothing happen !" or why "the
application is very low to start up!" (due to a pointcut matching
almost every single instruction f.e.). The output will print message
about "earlymatch" and "match". An early match means that there might
be a match but that further analysis of the class beeing weaved is
needed. A match thus means a pointcut match (thus an actual join
point). When a mixin is used, you only see early matches.

Alex

On 6/21/05, Benjamin Livshits <[email protected]> wrote:
> I am trying to use load-time weaving with Java 5 agent support to apply
> aspects to Eclipse. Things appear to go okay while the main class loader is
> active, however, soon thereafter, Eclipse spawns a new class loader. It
> seems from then on pointcuts don't hit anymore.
> 
> Has anybody tried something like this? IS there a way to get around this?
> 
> Thanks much in advance.
> 
> -Ben
> 
>