An XSL-FO processor plug-in is used by process commands in XMLmind XML Editor - Commands (and more specifically element processFO in XMLmind XML Editor - Commands) to invoke a third-party XSL-FO processor. For example, an XSL-FO processor such as Apache FOP is used to convert to PDF the XSL-FO intermediate file created by the → → process command.
Like all plug-ins, an XSL-FO processor plug-in is not declared anywhere. It is dynamically discovered and loaded during the startup of XXE (more info in Section 1, “Dynamic discovery of add-ons” in XMLmind XML Editor - Configuration and Deployment) provided that it complies with the following conventions:
The code of the XSL-FO processor plug-in must be contained in a JAR file having a name ending with "_foprocessor.jar".
This JAR file must contain a META-INF/services/com.xmlmind.foprocessor.FOProcessor file containing the name of the class implementing interface com.xmlmind.foprocessor.FOProcessor.
For example, fop1_foprocessor.jar contains META-INF/services/com.xmlmind.foprocessor.FOProcessor which contains com.xmlmind.xmleditext.fop1_foprocessor.FOP.
Implement interface com.xmlmind.foprocessor.FOProcessor.
If you plan to implement an XSL-FO processor plug-in and need an example showing how this can be done, please send an email to <xmleditor-info@xmlmind.com> and we'll provide you with the full source code of the "Apache FOP 1.x XSL-FO processor plug-in".