RE: [aspectwerkz-dev] include element in aop.xml
"Jonas Boner" <[email protected]>
| Newsgroups | gmane.comp.java.aspectwerkz.devel |
|---|---|
| Message-ID | <[email protected]> |
It is the case for all weaving modes, both offline and online. /Jonas > -----Original Message----- > From: Eugene Kuleshov [mailto:eu-E/[email protected]] > Sent: Thursday, July 15, 2004 12:55 PM > To: [email protected] > Subject: Re: [aspectwerkz-dev] include element in aop.xml > > Jonas Boner wrote: > > >> Please correct me if I'm wrong, but my understatanding of the AW > >>online mode is that all classes in include is being > instrumented and > >>then within instrumented classes advices added as per binding > >>configuration. > >> Basically in my case I don't need dynamically add/remove > advices. > >>So I'm lookin for possibility to reduce number of instrumented > >>classes. > > > > This is wrong. > > > > In AW only the classes that has a join point that matches a > pointcut > > in your definition will be instrumented. > > > > So the include/exclude package is only a convenience > construct, sort > > of system level 'within' and 'NOT within'. > > Is it correct for both bytecode weaving and hotswap modes? > I'm using online mode with JDK 1.3 to run Weblogic7 under AW. > > regards, > Eugene > > >