Message-ID: <691857407.41216.1371644735326.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_41215_215914155.1371644734770" ------=_Part_41215_215914155.1371644734770 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
BTM ships with SLF4J which is a logging facade much like Apache Comm= ons Logging but it's safe to use in application servers unlike Commons Logg= ing which suffers from complex classloader issues.
Much like Commons Logging, SLF4J can route the log requests to many diff= erent implementations including the two most common ones: JDK 1.4 and Log4J.
By default, BTM is shipped with slf4j-jdk14-1.5.8.jar which is the the <= a href=3D"http://jcp.org/aboutJava/communityprocess/review/jsr047/" class= =3D"external-link" rel=3D"nofollow">JSR 047 logging API (aka JDK 1.4 loggin= g) wrapper. If you want to use another logger, simply delete the slf4j-= jdk14-1.5.8.jar file and replace it with any one from this list:
You will also need to put the slf4j-api-1.5.8.jar file in your classpath as well, no ma= tter which one of the above jars you choose.
Those jars come from the 1.5.8 distribution of SLF4J.
This feature appeared in BTM 1.3.3 and is not available in earlier v= ersions.
If your logging implementation supports MDC (like Log4J does for instance) BTM will push the tr= ansaction's GTRID in the logger's MDC when a transaction is created.
The GTRID is pushed under the
me. You can make it appear in your Log4J logs by adding it to the
When using a different implementation than Log4J, please refer to your l= ogger's documentation to understand how to make use of this feature.
------=_Part_41215_215914155.1371644734770 Content-Type: image/gif Content-Transfer-Encoding: base64 Content-Location: file:///C:/shim.gif R0lGODlhAQABAIAAANvf7wAAACH5BAEAAAAALAAAAAABAAEAAAICRAEAOw== ------=_Part_41215_215914155.1371644734770--