concept place in category aspectj

appears as: place, place, places, places
AspectJ in Action, Second Edition

This is an excerpt from Manning's book AspectJ in Action, Second Edition.

  • A module to express all crosscutting constructs— Because the end goal of AOP is to have a module that embeds crosscutting logic, you need a place to express that logic. The aspect construct provides such a place. An aspect contains pointcuts, advice, and static crosscutting constructs. It may be related to other aspects in a similar way to how a class relates to other classes. Aspects become a part of the system and use the system (for example, classes in it) to get their work done. We’ll examine AspectJ’s implementation of aspect in chapter 6.
  • Listing 10.3. The Order class with conventional tracing
    package ajia.domain; import ... ... public class Order extends DomainEntity { ... private Logger logger = Logger.getLogger("trace"); public void addItem(Product product, int quantity) { logger.log(Level.INFO, "Entering [Order.addItem]"); ... } public void removeItem(Product product, int quantity) { logger.log(Level.INFO, "Entering [Order.removeItem]"); ... } public boolean isPlaced() { logger.log(Level.INFO, "Entering [Order.isPlaced]"); ... } public void place() { logger.log(Level.INFO, "Entering [Order.place]"); ... } ... }

    Note that is it easy to fix the problem by calling em.flush() in place of issuing an error. But doing so forces inclusion of that aspect in production.