JBoss Enterprise Application Platform Common Criteria Certification ...

18 Chapter 3. Logging
The first way is to explicitly enable it in your code.
SessionFactory sf = new Configuration()
.setProperty("hibernate.show_sql", "true")
// ...
.buildSessionFactory();
Alternately, you can configure Hibernate to send all SQL messages to log4 j, using a specific facility:
log4j.logger.org.hibernate.SQL=DEBUG, SQL_APPENDER
log4j.additivity.org.hibernate.SQL=false
The additivity option controls whether these log messages are propagated upward to parent
handlers, and is a matter of preference.
3.2.2. Transaction Service Logging
The TransactionManagerService included with the Enterprise Platform handles logging differently than
the stand-alone Transaction Service. Specifically, it overrides the value of the
com.arjuna.common.util.logger property given in the jbossjta-properties.xml file, forcing use of
the log4 j_releveler logger. All INFO level messages in the transaction code behave as DEBUG
messages. Therefore, these messages are only present in log files if the filter level is DEBUG. All other
log messages behave as normal.