当类层次结构不是线性时,在基接口上定义时不会触发方面。
最有趣的是:将委托实现(参见最后一个代码块)添加到实现的父类时,测试变为绿色(按预期触发了方面)。
问题:为什么它不像示例中描述的那样工作,为什么它与委托实现一起工作?
示例(抱歉,找不到更短的示例):
测试:
@Autowired
private TheInterface underTest;
private static boolean aspectCalled;
private static boolean implementationCalled;
@Test
public void aspectTest() throws Exception {
aspectCalled = false;
implementationCalled = false;
underTest.doSomething();
assertTrue("Implementation not called!", implementationCalled);
assertTrue("Aspect not called!", aspectCalled);
}
方面:
@Aspect
@Component
public static class MyAspect {
@Before("execution(* *..SpecializedInterface+.doSomething())")
public void applyAspect() {
aspectCalled = true;
}
}
接口:
public static interface TheInterface {
void doSomething();
}
public static interface SpecializedInterface extends TheInterface {
// inherits doSomething
// defines some other methods
}
抽象实现(模板模式):
public static abstract class BaseTemplate implements TheInterface {
abstract void doOneStep();
@Override
public void doSomething() {
// do some stuff and
doOneStep();
}
}
public static abstract class SpecializedTemplate extends BaseTemplate implements SpecializedInterface {
// some other methods
}
实现bean:
@Component
public static class TemplateImplementation extends SpecializedTemplate {
@Override
void doOneStep() {
implementationCalled = true;
}
}
(如果您有兴趣:测试设置:)
@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguration(classes = MyConfig.class)
public class AopTest {
@Configuration
@EnableAspectJAutoProxy
@ComponentScan(basePackageClasses = AopTest.class)
public static class MyConfig {
}
...
丑陋的解决方法:将此代码段添加到 SpecializedTemplate
@Override
public void doSomething() {
super.doSomething();
}
那么,为什么需要这种解决方法?