When you change the transformation language of a MapForce mapping, certain features may not be supported for that specific language. The following table summarizes the compatibility of mapping formats and transformation languages in MapForce Professional Edition.
Remarks:
•Built-in means that you can execute the mapping by clicking the Output tab in MapForce or run it with MapForce Server.
Mapping format |
XSLT 1.0 |
XSLT 2.0 |
XSLT 3.0 |
XQuery |
C++ |
C# |
Java |
BUILT-IN |
|
|---|---|---|---|---|---|---|---|---|---|
XML1 |
 |
|
|
|
|
|
|
|
|
CSV and text |
|
|
|
|
|||||
Binary files |
|
||||||||
Databases2 |
ADO |
|
|
|
|||||
ADO.NET |
|
|
|||||||
JDBC |
|
|
|||||||
Native SQLite |
|
||||||||
Native PostgreSQL |
|
||||||||
ODBC |
|
|
|
|
|||||
Footnotes:
1.XML with digital signatures processing is supported only by MapForce Enterprise Edition using BUILT-IN as a transformation language.
2.Limitations apply depending on the database type and the target environment. For more information, see Database mappings in various execution environments.
