concept authorization aspect in category aspectj

This is an excerpt from Manning's book AspectJ in Action, Second Edition.
Crosscutting concern implementations often require some behavior specific to the advised type to be invoked from advice. For example, an authorization aspect may need the roles that are authorized to access specific functionality. In many cases, the base aspect can leverage join point context to deduce the needed behavior. For example, the authorization aspect might use a method name as a key into a map to obtain the security role (you’ll use such a scheme in chapter 15). But in other cases, complex logic may be needed to obtain the role. Perhaps the amount involved in a banking transaction determines the role needed to perform the operation. In such cases, you need collaboration from classes not only in supplying the pointcuts but also in augmenting the behavior.
An authorization aspect ensures that the user has sufficient privileges to access the advised join point. As usual, you have two choices for weaving in the authorization logic: proxy-based or byte code–based weaving. To accommodate both choices, you’ll use the @AspectJ syntax, exactly as you did for authentication.