FM12 maker.ini -- XmlUtilities client

[rombanks]

Hello fellows,

Does anyone know what the following structured FM12 client does and what the configuration options are?

XmlUtilities=Standard, Utilities for XML, fminit\xmlutils.dll, structured

The FM12 INI Reference Guide does not explain anything about this (and many other) clients. The documentation is superficial.

We had a problem with running Saxon until we commented out the XmlUtilities line in maker.ini.

Thanks for your input in advance!

[Thread moved by moderator]

[Jeff_Coatsworth]

May want to ask over in the Structured forum – this one is the Unstructured one. You may also want to consult Klaus Daube’s site – he’d got detailed documentation on maker.ini settings.

[rombanks]

Hi Jeff,

You are right. Is it possible to move this thread to the right forum?

Klaus 's resource is indeed good, but it does not mention this option.

Best wishes,

Roman

[anarora]

This is a client where many xml related processing is handled like entity-resolution, new-xml creation, smart paste etc. Pls don't comment-out this entry as it may have impact on other workflows.

If you are facing any problem in Saxon specifically, try changing your processor to Xalan.

Regards,

Anchal

FM Engineering

[rombanks]

Hi Anchal,

Thank you for your response!

If I set Xalan as the default XSLT engine, it does not solve the issue. The issue is that when I try to open an XML file in structured FM, I get the following error:

XSLT Processor Messages

org.xml.sax.SAXException: FWK005 parse may not be called while parsing.

javax.xml.transform.TransformerException: org.xml.sax.SAXException: FWK005 parse may not be called while parsing.

javax.xml.transform.TransformerException: org.xml.sax.SAXException: FWK005 parse may not be called while parsing.

Transformation Aborted.

The issue is only "resolved" by commenting out the XmlUtilities option.

Best regards,

Roman

[anarora]

Hi Roman,

That may be because you are using a pre-xslt in your structured application that is not correct and leading to this error. Pls check if the xml file contain a stylesheet pi or the structured application contains a construct Stylesheets. If yes, they would be automatically applied on file open. You can remove those entries from your file or if you really need to use xslt, pls correct any errors in the xsl file.

Regards,

Anchal

[rombanks]

Hi Anchal,

I appreciate your response!

It's interesting that there is no such issue in FM10 -- everything works OK. So theoretically, the stylesheet should have been compatible with FM12 as well. BTW, what do you mean by "a construct Stylesheets"?

Thanks,

Roman

[anarora]

That must be because we have updated the xslt processor from xalan-c to xalan-j (java based) and your xsl may not be compatible with it. Pls see the attached screenshot for what I mean with Stylesheet construct inside an XML application.

[rombanks]

Hi Anchal,

Thank you for your response! This sheds some light on the issue.

What's the advantage of the Java-based Xalan? Java was always known to be a major memory consumer.

Is it possible to use Xalan C++ with FM12?

Best regards,

Roman