Configure the processor definition file used by the processor. The format of the looks like the following:

${typeMape}=>${relative_path_from_document-root_2_definition}

You can use add more than one processor. They are restored in a processor chain and run next to each other.

You don't necessarily have to set the processor definition in the configuration. TomKit has the possibility to read the processor definitions directly from the processed file. This looks like the following:

Configure the content provider which provides the content to the transformer chain as its name indicates. If you don't configure a AxContentProvider there are 2 possibilities:

default response handler

the default response handler of apache is used. This means caching is avaiable out of the box and done automatically by TomKit for you

another apache-module

a content handler is another apache-module e.g. PerlResponseHandler. Although very cool it has the disadvantage that caching is not available out-of-the-box. To use caching possibilities TomKit provides to you your ResponseHandler has 2 possibilities:

This turns off AxKit-Compilance which is not given out-of-the box. Chdir to document-root is possible automagically because of threading issues. Please note that running with no AxKit-Compilance may be faster and can be achieved by evaluating the special parameter "_TOMKIT_DocumentRoot" which is passed to XSLT-Processors.

This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself, either Perl version 5.8.6 or, at your option, any later version of Perl 5 you may have available.