Re: Re: Online mode architecture

We don't plan yet to have bytecode kit independance for AspectWerkz as a
whole so we won't add asm.jar to the project for now. I would rather have
this kind of things as separate jars.
Having asm.jar in the project will be the way to go if all the AspectWerkz
transformer stack (currently implemented with BCEL) would be ported to ASM
(or other bytecode kit as well). But unless someone wish to hack it, it
won't be in the todo list until some stage.

Tips: notice that there is a specific snip to support IBM WSDK in the
BCEL..Impl. Could be good to have it as well in ASM implementation
(defineClass0 has extra args compared to standard SUN JDK).

Alex

> Alex wrote:
>> For the short story about this, this part was at the beginning an
>> autonomous project I started on sourceforge. I donated it to Jonas /
>> AspectWerkz when I joined AspectWerkz.
>> This part is not documented as a standalone one since the primary goal
>> of
>> AspectWerkz is not this one. But getting in the source you will see that
>> it is fairly easy to define your own ClassPreProcessor and even use
>> another bytecode kit (other than bcel), keeping all low level weaving
>> features (classloader hierarchy support, offline compilation, native
>> hook,
>> bytecode kit independance, lightweight).
>> For further (but out of date and less featured) information, go thru my
>> old http://besee.sourceforge.net/
>
> Thanks for the information.
>
> I'm going to reimplement ClassLoaderPreProcessorImpl using ASM
> (http://asm.objectweb.org/). If you don't mind adding ASM as a
> compile-time
> dependency (it is only 20K) I would prefer that ASMClassLoaderPreProcessor
> become part of aspectwerkz-core.jar.
>
> Chris
>
>
> _______________________________________________
> aspectwerkz-devel mailing list
> aspectwerkz-devel-81qHHgoATdGxIXFVlbCvtR2eb7JE58TQ@public.gmane.org
> http://lists.codehaus.org/mailman/listinfo/aspectwerkz-devel
>