Dear M. Shafie,
The problem we have is not directly related to XMLMind itself, but more
likely to the version of Saxon (?) bundled with release 4.8 of XMLMind.
I'll try to explain the issue as simply as I can, many thanks for any
clue/advise you would have.
Below is the status of problem:
Apart from our interactive work with XMLMind (works great), we also use
XMLMind as a batch tool to transform our XML files.
Instead of delivering our own copy of Saxon jars and XML catalogs, we
use those included in the XMLMind distribution, pointed to below by
variable *XXE_INSTALL_DIR*
Let's suppose we wrote a XSL stylesheet to process DocBook documents,
e.g. /mystylesheet.xsl/, we used to setup things like this (UNIX example):
% export XXE_INSTALL_DIR=/scr/softs/xxe-pro-x.y.z
% export XML_CATALOG_FILES=$XXE_INSTALL_DIR/addon/config/catalog.xml
% export
CLASSPATH=$XXE_INSTALL_DIR/bin/saxon9.jar:$XXE_INSTALL_DIR/bin/resolver.jar
And then process our DocBook documents (e.g. mydbk.xml), this way using
Saxon-9:
% java -Dxml.catalog.files=$XML_CATALOG_FILES net.sf.saxon.Transform
-r:org.apache.xml.resolver.tools.CatalogResolver
-x:org.apache.xml.resolver.tools.ResolvingXMLReader
-y:org.apache.xml.resolver.tools.ResolvingXMLReader mydbk.xml
/mystylesheet.xsl
/This has been working since Saxon-9 is bundled with XMLMind, up to
*XMLMind release 4.8.0*, where it ceased to work. The transformation
hangs before processing actually starts, presumably because one of the
resources needed is fetched from the network...
Our guess is that this is due to some change in the version of Saxon
bundled with XMLMind 4.8.0 ?
Many thanks for your help,
Best regards.
Philippe.
--
XMLmind XML Editor Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
