This topic has not yet been written. The content below is from the topic description.
Logging Overview JBoss AOP allows you to view important information during the weaving process. We will see how to turn logging on, and have a look at how once turned on we can choose log4j or System.out as the underlying logging mechanism. The System.out logging meschanism will print everything regardless of logging level, while the log4j mechanism allows for more control of which classes you want to be output. If using log4j, the classes in the org.jboss.aop package and sub-packages are where the logging is done. All the examples require jboss-logging-spi.jar to be on the classpath, whether run without logging, or with System.out logging or log4j logging. We will see later how, once logging is turned on, the inclusion of jboss-logging-log4j.jar and log4j.jar enable the log4j logging mechanism. When run in the JBoss Application server, both jboss-logging-log4j.jar and log4j.jar will be available, so if logging is enabled it will happen via log4j. Example on how to do this with maven is shown on the bottom of this page.