[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [aspectj-users] Drawbacks of AOP
|
I have the same concerns. Tools can help, but until the need for class
file weaving is removed (by what I don't know?), it is difficult to use
AOP in a production environment. We only use AOP after we have
decompiled the aspect and the weaved class to ensure it does exactly
what we want and is optimized properly. Obviously, this takes extra
time but is worth it in certain situations.
Thanks... Sean
P.S. Anyone have thoughts on what will replace class file weaving?
Will there be an AOP API incorporated into the VM? Will the ClassLoader
and class file format be changed? Any predictions?
-----Original Message-----
From: aspectj-users-admin@xxxxxxxxxxx
[mailto:aspectj-users-admin@xxxxxxxxxxx] On Behalf Of Pedone, Tim
Sent: Monday, April 14, 2003 5:37 PM
To: 'aspectj-users@xxxxxxxxxxx'
Subject: [aspectj-users] Drawbacks of AOP
When I first discovered AOP, I was quite enamored with it. It seemed
that
it solves quite a few common problems; however, I also wanted to see
what
other people thought of it so I did some research and came across an
issue
that I think needs addressing.
This issue is pointcut visibility. The problem is that a programmer
looking
over some code may not realize that the code is cut by an Aspect. He
may
copy the code into another method and the code may or may not work the
same
depending on how the pointcut is defined. Or he may make a change to the
code not fully realizing the impact of the change because of the
pointcut.
I'd like to get some feedback regarding this from the AOP community.
I'm
trying to introduce AOP here are work but want to make sure I understand
the
shortcomings as well as the benefits.
Thanks,
Tim
_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/aspectj-users
