CodeMonitor^TM for Java is implemented with our ClassWeaver^TM technology, and injects monitoring code into existent Java bytecode. Because it is not a logging tool in itself, it uses the standard APIs defined by different logging toolkits or logging systems. It therefore complements these toolkits and systems, and is very easy to integrate in set-ups where these toolkits and systems are already in place.

Some of these logging tools try to provide a solutions in their own, others try to integrate others, some mix. It is difficult to choose between the “best” toolkit and system, and to commit to one or another may become a severe restriction for further developments, because changing logging statements written in source-code is time-consuming. By construction CodeMonitor^TM for Java doesn't suffer from these restrictions. Switching between the APIs of different logging tools is a matter of minutes, and not days or weeks.

The following list of logging tools for the Java platform is not exhaustive, and not every listed tool is directly usable by CodeMonitor^TM for Java, but it tries to help you understand our development road-map. If you are interested in the integration of one of these logging tools or has developed an own logging tool, which you like to be integrated into CodeMonitor^TM for Java, don't hesitate to contact us.

Java Logging API .  This logging API was introduced by Sun Microsystems with JDK 1.4 and is part of the standard distribution of the Java platform since then. This logging API is directly supported by CodeMonitor^TM for Java.

Log4J .  One of the well-known logging toolkits is Log4J. It was developed as part of Apache's Jakarta project. Log4J is directly supported by CodeMonitor^TM for Java.

LogKit . A newer and somewhat less well-known logging toolkit also by Apache is the LogKit, which was developed as part of the Avalon-project. LogKit is directly supported by CodeMonitor^TM for Java.

Jakarta Commons Logging Component .  The Logging package is an ultra-thin bridge between different logging libraries. Commons components may use the Logging API to remove compile-time and run-time dependencies on any particular logging package, and contributors may write Log implementations for the library of their choice. This API is currently not supported by CodeMonitor^TM for Java. This is planned for a future release.

JMyra Observer .  The JMyra Observer is a logging system developed by the SDS IN-Net GmbH, Germany. It supports Log4J and JDK logging, and is therefore supported by CodeMonitor^TM for Java.

SuperLogging .  A logging system for J2EE/EJB developed by Acelet Corporation, USA. The API of SuperLogging is currently not supported by CodeMonitor^TM for Java. This is planned for a future release.

jLEA .  Journaling & Logging Enterprise Applications is a logging system developed by The Object Company GmbH, Germany. The API of jLEA is currently not supported by CodeMonitor^TM for Java. This is planned for a future release.

jLog 2.0 .  The jLog is a strictly Java-based framework for logging and alerting, developed by JTrack GmbH, Switzerland. The API of jLog is currently not supported by CodeMonitor^TM for Java. This is planned for a future release.