I/O Types

Introduction

Various protocol types are available for use with:

inputA
inputB
configuration
output

With inputs (inputA, inputB, & configuration) you can use all of the available types.

However, with output, only File is available.

HTTP

HTTP or HTTPS URIs can be specified and the comparator will try to load the specified file. This may involve the downloading of additional entities or other resources that are referenced by the specified file. Examples include:

DOCTYPE dtds
XML schema files using xsi association
General external XML entities referenced in the file
Resources specified using the XInclude mechanism

multipart/form-data

CODE

.....
Content-Disposition: form-data; name="A"
http://www.example.com/file1.xml
--boundary
.....

File

A file path (on the server) can also be used to specify the input, output, and configuration locations. For example:

multipart/form-data

To use File I/O with multipart/form-data, set the Content-Type to text/plain:

CODE

.....
Content-Disposition: form-data; name="A"; Content-Type: text/plain;
/Users/exampleUser/Documents/file1.xml
--boundary

Strings

Raw XML can be used from multipart/form-data. To specify raw XML use application/xml, text/xml or text/html as the Content-Type of the part, for example:

CODE

Content-Type: multipart/form-data; boundary=boundary-id
Content-Length: number_of_bytes_in_entire_request_body
--boundary-id
Content-Disposition: form-data; name="inputA"; Content-Type: application/xml;
<root><a/></root>
--boundary-id
Content-Disposition: form-data; name="inputB"; Content-Type: application/xml;
<root/>
--boundary-id