anchor.diff:  We have already seen how to bind the returned value or exception value (using after
   returning and after throwing advice). To make argument values available to the advice
   body, you can use the binding form of `args`. If you use a parameter name in place of a
  -type name in an args expression, the value of the corresponding argument is passed as
  +type name in an `args` expression, the value of the corresponding argument is passed as
   the parameter value when the advice is invoked. An example should make this clearer.
   Suppose you want to advise the execution of DAO operations that take an `Account`
   object as the first parameter, and you need access to the account in the advice body.
  
positive.code: 
  When deploying multiple web applications within the same container, ensure that each
  web application loads the types in `spring-aspects.jar` by using its own classloader
  (for example, by placing `spring-aspects.jar` in `'WEB-INF/lib'`). If `spring-aspects.jar`
  is added only to the container-wide classpath (and hence loaded by the shared parent
  classloader), all web applications share the same aspect instance (which is probably
  not what you want).
  
negative.code: Second, it makes the actual `Account` object available to the advice through the `account`
  parameter.
  
  Another way of writing this is to declare a pointcut that "provides" the `Account`
  object value when it matches a join point, and then refer to the named pointcut
  from the advice. This would look as follows:
  
  