RE: [aspectwerkz-dev] tracing to the console

The CL is modified in a pre-step if you run HotSwap mode. This is something we want to get away from since it is slow (requires -Xdebug) and overly complex (and differs in impl between the JVMs).
The preferred choice is the JMAPI in jrockit and JVMTI in 1.5. 

I don't think that I want to add a generic join point shadow to the defineClass in the CL since it will add additional overhead that would not be much of use. This could of course be user configurable. So, sure, it can be added as an option if you are running the HotSwap mode (or the offline).

But as I said, we are moving away from this option.

/Jonas

-----Original Message-----
From:	eu [mailto:eu-E/[email protected]]
Sent:	Tue 7/13/2004 8:48 PM
To:	[email protected]
Cc:	
Subject:	Re: [aspectwerkz-dev] tracing to the console

Jonas Boner wrote:

> Then you would have to do post-compilation of rt.jar.

   Hmm. That is confusing.

   I see that ClassLoader class is being instrumented (at least when I 
start application using aspectwerkz.bat), why not leave joinpoint in there?

   regards,
   Eugene


> -----Original Message-----
> From:	eu [mailto:eu-E/[email protected]]
> Sent:	Tue 7/13/2004 7:51 PM
> To:	[email protected]
> Cc:	
> Subject:	Re: [aspectwerkz-dev] tracing to the console
> 
> Alex wrote:
> 
> 
>>The AOP container is designed to avoid to hook directly in the classloader
>>class. I don't want to hook in classloaders. It was already complex to
>>enable class load time weaving.
> 
> 
>    Hmm. Is there are any way to put a custom advice to something like 
> execution(* java.lang.ClassLoader+.new(..)) ?
> 
>    regards,
>    Eugene
> 
> 
> 
>