org.springframework.config.java
Class AspectTests.ConfigWithAspects

java.lang.Object
  extended by org.springframework.config.java.AspectTests.ConfigWithAspects
Enclosing class:
AspectTests

public static class AspectTests.ConfigWithAspects
extends Object

Notice how the Configuration class is also an Aspect? This is strange, and I believe unintuitive/surprising for users of Spring AOP coming from the XML world. As a user, I would expect that I would define my Aspects and then somehow expose them as beans within my Configurations. In this example, the advice methods (logGetNameCall, logGetNameCalled) are defined inline with the Configuration. This is convenient, perhaps, but it shouldn't be the only way to do it.


Constructor Summary
AspectTests.ConfigWithAspects()
           
 
Method Summary
 TestBean foo()
           
 void getName(TestBean testBean)
           
 void logGetNameCall(TestBean testBean)
           
 void logGetNameCalled(TestBean testBean)
           
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Constructor Detail

AspectTests.ConfigWithAspects

public AspectTests.ConfigWithAspects()
Method Detail

logGetNameCall

public void logGetNameCall(TestBean testBean)

logGetNameCalled

public void logGetNameCalled(TestBean testBean)

getName

public void getName(TestBean testBean)

foo

public TestBean foo()


Copyright ? 2005-2008 Spring Framework. All Rights Reserved.