| Sign In/My Account | View Cart |
| Article: |
An Introduction to Aspect-Oriented Programming with the Spring Framework, Part 1 | |
| Subject: | Automatic Swap of Target Class | |
| Date: | 2006-03-30 00:53:13 | |
| From: | russellmiles | |
|
Response to: Automatic Swap of Target Class
|
||
| To my knowledge, in Spring you'd be best advised to do this sort of implementation replacement behind an interface anyway, and then to use regular AOP to change the actual implementation class. This is the approach advocated by the framework and is a best practice anyway, particularly for what you are attempting to do. | ||
Showing messages 1 through 3 of 3.
Automatic Swap of Target Class
I am attempting to replace ClassA target to ClassB. So the pattern that I am trying to use is (if the package is com.xx), pointcut on com.xx.Class*, anything with Class on their name within the package will be replaced with ClassB. And ClassA is not an interface.
I have used advises via methods,also using interfaces in spring, but for class, I only have seen it in AspectJ.
It seems like jointpoints in spring framework is just limited to methods, and not classes yet. Here is the excerpt from the spring :
"Joinpoint: Point during the execution of a program, such as a method invocation or a particular exception being thrown. In Spring AOP, a joinpoint is always method invocation. Spring does not use the term joinpoint prominently; joinpoint information is accessible through methods on the MethodInvocation argument passed to interceptors, and is evaluated by implementations of the org.springframework.aop.Pointcut interface."
At the moment, I am still looking at the AspectJ document, coz I might just overlooked this.
Thanks for the reply