Claus Rasmussen wrote: > I'm loading a JAR file in my configuration like this: > > <load location="path/to/jarfile.jar" /> > > It defines some extensions I need to call from xslt when doing my processing. > > When I run the transform, the extensions aren't picked up (I'm checking with > function-available() ), though everything works fine when I just run saxon > from the command line and include my jar file in the classpath.
This should work. For example, Saxon extensions written by Norman Walsh are loaded and used by default in XXE when converting DocBook documents to HTML and to XSL-FO. See <XXE_install_dir>/config/docbook/xslMenu.incl: --- <load location="docbook-xsl-saxon.jar" /> --- They are used, for example, when you convert a <programlisting> with attribute linenumbering="numbered" to HTML. Also, note that in XXE, bundled configurations are not treated specially compared to user custom configurations. Therefore, if it works for DocBook, it should work for your configuration. I don't know why, but your jarfile.jar is probably not loaded: * Check the validity of your configuration file. * Is your configuration file listed by the dialog box displayed by "Help|About XMLmind XML Editor"? * Run XXE with a console to check that you have no link errors (i.e. your jar file may reference code found in your classpath, but not in XXE classpath, which is dynamically built at startup time).
