The latest version of MDF is release 0.3. Features of this release include:
- Bug fixes for the SimpleXTMMapper module which prevented associations from being correctly generated under certain circumstances
- A new ConfigurableXTMMapper module which enables topic map generation to be configured from an XML file.
- Configurable logging output using Log4J
- Fixed MDFApp to use name-spaced attributes.
Both binary and source distributions are available.
IMPORTANT for users of version 0.2.1 – The MDFApp application now requires that the ‘key’ attribute of mdf:property elements be correctly namespaced (i.e. it shoul d be prefixed with the same prefix as the property element itself). Any existing MDF scripts must be updated to correctly namespace the key attribute.
Both packages include all of the libraries that you need to build the package and to create and run your own MDF processing chains.
MDF is distributed under the same license as TM4J – the Apache Foundation license. You can read the license text here
MDF can be built by executing either
build.sh (on Linux) or
build.bat (on Windows). You must execute this script from the base directory of the MDF code (the directory which contains the file
build.xml). All of the libraries needed to build the current set of MDF modules are included in the source distribution.
MDF is primarily a developer’s toolkit. There is one sample command-line application, com.techquila.mdf.impl.basic.MDFApp which reads an MDF processing chain definition from an XML file and executes it. See the module documentation for more information about the format of the configuration file it uses and how to run the application.
MDF makes use of the Log4J for reporting debug, informational, warning and error messages. By default, MDFApp and the processing modules are all fairly verbose. However, the level of output of each component is easily configured by creating a file named log4j.properties and placing it in a directory which is on the normal Java class loading path (e.g. in a directory on your CLASSPATH). To configure the level of output of the application as a whole, add the following line to log4j.properties:
where level is one of DEBUG, INFO, WARN, ERROR or FATAL
(Note that you should choose just one of the values shown above). This will configure the logging of the application as a whole to report only those messages of the specified level or greater.
You can configure individual modules to be more or less verbose by a line such as:
where module-class-name is the full Java class name of the module in question and level is one of DEBUG, INFO, WARN, ERROR or FATAL.