Please enable JavaScript to view this site.

Altova MapForce 2022 Enterprise Edition

You can change the document-specific settings of the currently active mapping design file in the Mapping Settings dialog box. This information is stored in the *.mfd file. To open the Mapping Settings dialog box, click Mapping Settings in the File menu (see screenshot below).

mf_ent_mapping_settings_dlg_zoom70

 

The available settings are described in the subtopics below.

Application name

Application name defines the prefix of the generated XSLT file or the name of the generated Java, C#, or C++ application.

Java base package name

This option is applicable when Java is selected as a transformation language. It defines the base package name for the Java output.

Make paths absolute in generated code

This check box affects all paths in mapping components, except paths to external library files (e.g., XSLT libraries). The check box defines whether the file paths should be relative or absolute in the generated program code, in MapForce Server Execution files (.mfx) and in mapping functions deployed to FlowForce Server. For more information, see Paths in Various Execution Environments.

Reference libraries with paths relative to the generated XSLT/XQuery files

This check box is applicable when the mapping language is either XQuery (available in MapForce Professional and Enterprise editions) or XSLT. This option is typically useful if your mapping references an XSLT or XQuery library, and you plan to generate XSLT or XQuery files from the mapping. Select this check box if you want the library paths to be relative to the directory of the generated XSLT or XQuery code. If the check box is not selected, the library paths will be absolute in the generated XSLT or XQuery code. See also Library paths in generated code.

Ensure Windows path convention for file path

This check box is applicable when the mapping language is XQuery (available in MapForce Professional and Enterprise editions), XSLT 2.0 or XSLT 3.0. The check box makes sure that Windows path conventions are followed. When you output XSLT 2.0, XSLT 3.0 or XQuery, the currently processed file name is internally retrieved using the document-uri function, which returns a path in the file://URI format for local files. When this check box is selected, a file://URI path specification is automatically converted to a complete Windows file path (e.g., C:\...) to simplify further processing.

Line ends

This combo box allows you to specify the line endings of the output files. Platform default is the specific default for the target operating system: e.g., Windows (CR+LF), macOS (LF), or Linux (LF). You can also select specific line ending manually. The settings you select here are important when you compile a mapping to a MapForce Server Execution file (.mfx) or when you deploy a mapping to FlowForce Server running on a different operating system.

XML Schema Version

This option allows you to define the XML schema version used in the mapping file. You can define if you always want to load the schemas conforming to version 1.0 or 1.1. Note that not all version 1.1 specific features are currently supported. If the xs:schema vc:minVersion="1.1" declaration is present, version 1.1 will be used; if not, version 1.0 will be used.

XMLSchemaVersionOn

If the XSD document has no vc:minVersion attribute or the value of the vc:minVersion attribute is other than 1.0 or 1.1, XSD 1.0 will be the default mode. Do not confuse the vc:minVersion attribute with the xsd:version attribute. The first attribute has the XSD version number, while the second attribute has the document version number. Changing this setting in an existing mapping causes the reloading of all schemas of the selected XML schema version and might also change its validity.

Web Service Operation Settings

The WSDL Definitions, Service, Endpoint and Operation fields are automatically filled if the mapping document is part of a Web service implementation.

 

© 2015-2021 Altova GmbH