[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [aspectj-users] Unexpected weaving
- From: "David Hatton (AT/LMI)" <david.hatton@xxxxxxxxxxxx>
- Date: Tue, 10 Oct 2006 15:35:36 +0200
- Delivered-to: firstname.lastname@example.org
- Thread-index: Acbsavw9b2b+j3RcQEqOLFP5vBdpSQAAZFrJAAD0ahA=
- Thread-topic: [aspectj-users] Unexpected weaving
Title: Unexpected weaving
the classes which end up being woven are IDL generated classes. These classes
all end up in a package called
com.ericsson.nms.cif.cs.Configuration (and further
aspect picks up on classes in com.ericsson.nms.cif.cs and other sub-packages but
not Configuration (as far as I can see).
bit complicated but here it is anyway ...
could get around this by not generating the IDL until the weaving is completed,
but I would prefer to understand what I'm doing wrong.
Can you give more details
like the aspect and the classes that appears to be woven even though they should
From: aspectj-users-bounces@xxxxxxxxxxx on
behalf of David Hatton (AT/LMI)
Sent: Tue 10/10/2006 8:52
I am encountering some problems with certain classes
being woven when not expected.
Looking at my aspects these classes should not match
any of the defined pointcuts, yet are being output as being woven when I run the
ANT iajc task in verbose mode.
Using AspectJ inbuilt into Eclipse it is showing
these particular classes as being un-affected by the aspect I have defined, i.e.
there are no cross-references being detected by the Eclipse plug-in.
Is there any way I can determine which advice is
affecting the classes concerned during the Ant task?