The following limitations exist for conversion of XML data to and from FML/FML32 buffers using the Xerces 3.2.3 parser delivered with Tuxedo.

• XML documents are treated as a constrained XML message set, and not as a flexible XML grammar. This constraint is based upon the definitions specified in the FML/FML32 header file.
• Digitally signed XML, FML or FML32 buffers fail signature checking when using automatic conversion. The tpenvelope() function for digital signatures can only be used during on-demand conversion.
• Parsing limitations are those inherited from the Xerces library.
• The Xerces parser does not support output XML DTD/Schema validation.
• Conversion between XML and FML/FML32 buffers does not necessarily create the exact same XML document as which you started. Tuxedo FML/FML32 buffers group equivalent field types within a buffer and bases output order on that grouping; therefore, specific element ordering based on input XML is lost. The Xerces parser cannot track FML/FML32 field input order, or control FML/FML32 field output order.

  Please note the following:

  • All input format structure is lost during XML conversion.
  • You can input a partial listing of view32 members to XML, However, when XML is converted to FML32, the FML32 output will include all view32 members defined in the view definition file.
• During automatic conversion, input XML root tag names are not saved and the default output root tag <FML Type="FML"> or <FML Type="FML32"> is used.