Difference between revisions of "XSLT style sheet"
From Commander4j Wiki
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| + | [[Category:Commander4j Middleware]] | ||
| + | |||
The middleware program uses XSLT extensively to transform XML documents from one format to another. In addition to the standard XML output the configuration also supports output to other types of file such as ASCII in columns, CSV files, Excel and so forth. To do this the output XML has to be formatted in a manner which the middleware program can interpret for the given format. This will be covered in the example mappings.<br> | The middleware program uses XSLT extensively to transform XML documents from one format to another. In addition to the standard XML output the configuration also supports output to other types of file such as ASCII in columns, CSV files, Excel and so forth. To do this the output XML has to be formatted in a manner which the middleware program can interpret for the given format. This will be covered in the example mappings.<br> | ||
<br> | <br> | ||
| − | The underlying XSLT engine used by the middleware application is | + | The underlying XSLT engine used by the middleware application is Saxon-B XSLT and Query Processor [http://saxon.sourceforge.net] - the open source version. A number of [[Extension Functions]] in the form of Java API calls are also used to enhance the functions available in SAXON. |
Latest revision as of 17:31, 20 January 2018
The middleware program uses XSLT extensively to transform XML documents from one format to another. In addition to the standard XML output the configuration also supports output to other types of file such as ASCII in columns, CSV files, Excel and so forth. To do this the output XML has to be formatted in a manner which the middleware program can interpret for the given format. This will be covered in the example mappings.
The underlying XSLT engine used by the middleware application is Saxon-B XSLT and Query Processor [1] - the open source version. A number of Extension Functions in the form of Java API calls are also used to enhance the functions available in SAXON.
