Compare XML Data

Operation Name

Compare XML Data

Function Overview

Check whether the content of input data match the specified data as XML.

Executed only when the log level is FINFO or lower. Not executed when the log level is INFO or higher. When you do not want it to be executed in operation phase, set the log level to INFO or higher.

Data Model

XML type.

Properties

For details on use of variables, refer to “Variables”.
Basic settings
Item name Required/Optional Use of variables Description Remarks
Name Required Not available Enter the name to show on the script canvas.  
Input data Required Not available Select a component on the script canvas.  
Required settings
Item name Required/Optional Use of variables Description Remarks
Assert condition Required Not available Select an assertion condition.
  • [Match]: (default)
    Verify that the input data match the specified data as XML. When the input data do not match the specified data as XML, an assertion exception will be raised.
  • [Not match]:
    Verify that the input data do not match the specified data as XML. When the input data match the specified data as XML, an assertion exception will be raised.
  
Expected XML Required Available Enter the expected XML data.  
Option settings
Item name Required/Optional Use of variables Description Remarks
Raise assertion exception when the order differs Optional Not available Select whether or not to raise an assertion exception when the order of elements existing in the same path as XML differs.
  • [Checked]:
    An assertion exception will be raised when the order of elements existing in the same path as XML differs among the input data and the specified XML data.
  • [Not checked]: (default)
    An assertion exception will not be raised when the order of elements existing in the same path as XML differs among the input data and the specified XML data.
  
Comment
Item name Required/Optional Use of variables Description Remarks
Comment Optional Not available You can write a short description of this adapter.
The description will be reflected in the specifications.		  

Mass Data Processing

Mass data processing is not supported.

PSP Usage

PSP is not supported.

Available Component Variables

Component variable name Description Remarks
message_category When an error occurs, the corresponding message code's category is stored.
  • Default value is null.
message_code When an error occurs, the corresponding message code is stored.
  • Default value is null.
message_level When an error occurs, the corresponding message code's severity is stored.
  • Default value is null.
error_type When an error occurs, the error type is stored.
  • Default value is null.
  • The error type will be in the following format.
    Example: “java.io.FileNotFoundException”
  • The contents that will be stored may vary depending on DataSpider Servista versions.
error_message When an error occurs, the error message is stored.
  • Default value is null.
  • The contents that will be stored may vary depending on DataSpider Servista versions.
error_trace When an error occurs, the error's trace information is stored.
  • Default value is null.
  • The contents that will be stored may vary depending on DataSpider Servista versions and client applications.

Specification Limits

None.

Major Exceptions

Exception name Cause Solution
InputDataNotFoundException [Input data] is not specified. Specify [Input data] or draw data flow.
InvalidPropertyConfigurationException [Expected XML] is not specified. Specify [Expected XML].
AssertionException Assertion failed. Check whether [Input data] matches [Expected XML] or not.