AOP and AspectJ Terminology
by
Join the DZone community and get the full member experience.
Join For FreeIn my recent blog on 10 minute concepts, I mentioned some of the terms
relating to AspectJ and AOP, which I never defined. This blog puts that
right and explains some of these terms below...
| AspectJ Term | Description |
| Aspect | A feature of
a program that is separate from, and not related to any specific part
of a program, but is woven throughout the fabric of the program so as to
be used by all or many parts of the program.... and this sounds really
vague. You can think of a program as a bunch of events, for example:
methods being called, objects being constructed etc. An aspect oriented
approach to programming, such as ApsectJ, really means creating some
mechanism where by you can call your method before, after or around some
other event, so as run some of your code, without the need to reference
this code from the event. |
| Join Point | A join point is the name given to one of the programmatic events as described above, eg calling a method or creating an object. In AspectJ, a joint point is really the specification of where/when in your program, your aspect code is running. For example, if your aspect code runs before a given method call, then the join point describes the signature and arguments of that method. |
| Pointcut | A set of related joint points. When program execution reaches one of the join points in the pointcut, then your aspect code will run. |
| Advice | This is the code that runs when program execution reaches a joint point in your pointcut. |
From http://www.captaindebug.com/2011/09/aop-and-aspectj-terminology.html
AspectJ
Opinions expressed by DZone contributors are their own.
Comments