2016/05/28 - Apache Tuscany has been retired.

For more information, please explore the Attic.

 Apache Tuscany > Home > DAS Overview > DAS Java > DAS Java Documentation Menu > DAS Java Developer Guide > RDB DAS Java > RDB DAS - User Guide > Tuscany.TuscanyJava.DAS Java Overview.Improved logging User List | Dev List | Issue Tracker  

Tuscany/TuscanyJava/DAS Java Overview/Improved logging

Logging Overview


Using log while contributting for Tuscany DAS code

  • While contributing to DAS code, please follow the following guidelines to add logging to your class
    Instantiate a logger
    - There is a logger factory available in org.apache.tuscany.das.rdb.util - To use it
    • private final Logger logger = LoggerFactory.INSTANCE.getLogger(MappingWrapper.class);

- To instrument your code with logging capabilities

    • if(this.logger.isDebugEnabled())
      • this.logger.debug("your debug message");

Note: As a performance enhancement, please surround your debug code with a check to see if debug is enabled or not.

Configuring DAS logging (log4j)

  • Configuring with Tomcat
    There are two ways to configure log4j in Tomcat :
    • - Having a global log4j.properties inside %CATALINA_HOME%\common\classes
      - Having a global log4j.properties inside your own web app at WEB-INF\classes

Sample log4j.properties

# Set root logger level to DEBUG and its only appender to A1.

log4j.rootLogger=INFO, A1

# A1 is set to be a ConsoleAppender.


# A1 uses PatternLayout.

log4j.appender.A1.layout=org.apache.log4j.PatternLayout log4j.appender.A1.layout.ConversionPattern=[DAS RDB] - %c{1}.%M (%L) : %m %n

# Print only messages of level WARN or above in the package com.foo.

log4j.logger.org.apache.tuscany=OFF ** For further information, please follow the link : Tomcat FAQ - Logging

website stats