There are some documentations about MulTEx:

• The revised german conference paper of NET.OBJECT Days 2000 about the key concept of causal chains and the other features of MulTEx.
• The corresponding revised german conference slides of NET.OBJECT Days 2000.
• The english API documentation of MulTEx (generated by JAVADOC).
• In the delivered source code archive are a) in package multex.demo some demonstration programs with their message text file b) test cases in JUnit-style, if you can name that "documentation".
• More details, plans, and version history are in the multex package description.

MulTEx is redistributable als open source software by the GNU LGPL.

Installation

• From 5d on it requires JRE 1.2, and was compiled and tested with JDK 1.4.0 on Windows NT. Some none-core files for use in other environments require these environments. The dependencies are:
  • multex.Swing.java, multex.demo.SwingFile.java: The utility for reporting an exception chain into a Swing dialog and its demo program requires JDK >= 1.2.2.
  • errorPage.jsp: This example error page for a Java Server Page container requires such.
  • Jdk1_4CauseGetter.java: Compiles only on JDK 1.4, but is deprecated and replaced by the up-/downward compatible ReflectionCauseGetter.
  • test/*.java: These test drivers use JUnit and are compilable only with JUnit >= 3.7.
• You have to guarantee, that the archive multexVv-class.jar is accessible via your classpath or is in your lib direcory.
• For debugging you should enable, that the source code archive multexVv-java.jar is accessible for source browsing by your IDE.
• The file MsgText.properties or the localized variants of it must be in the actual working directory in order to access an internationalized message text for an exception, if you use static internationalization. See {@link multex.MsgText.setInternationalization(boolean)}.