Oh.. now I understand why AspectJ does it this way. Thanks!
In my project, I am using the Soot (http://www.sable.mcgill.ca/soot/)
tool for injecting code directly into the .class files.
Because of the Soot's syntax, it does get difficult to write and
maintain the code so
I was wondering if it would become easier by using AspectJ.
AspectJ does have a simple syntax but I think performance will suffer
as AspectJ introduces extra classes and methods and performance is key
to my project.
Is there any published material comparing the performance of Soot and
AspectJ tools?
----- Saurabh
On 03/27/2009 10:22 PM, Andy Clement wrote:
No, the inter type declaration is logically part of the
aspect and so
it continues to live there. AspectJ isn't for splicing new methods
into existing
classes. It is for saying: I have this concern that I am expressing as
an aspect and for some method invocations sent to some target type, I
want the aspect to answer them.
Does the existence of the aspect class files cause a problem?
Andy.
2009/3/27 Saurabh Shukla <sshukla@xxxxxxxxxxxxx>
Hello,
I have just started working on AspectJ and I find that the ajc does not
inject the body of inter-type method declarations into the target .class
file.
e.g. If the aspect Aj.aj is adding a method to the class A.java then
Aj.class contains the
body of the method.
Is there a way to completely eliminate Aj.class and inject all the
methods along with their bodies directly into A.class?
Thanks,
----- Saurabh
_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aspectj-users
_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aspectj-users
|
