Official |[Assertion] Compare XML Data

Operation name

Compare XML Data

Function overview

Checks whether the contents of the input data and the contents of the specified data match as XML.

Note

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

Data model

The data model of this component is XML type.

Properties

= Remarks =

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 a name that is used 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 and the specified data match as XML. When the input data and the specified data don't match as XML, an assertion exception will be thrown. Not match Verify that the input data and the specified data don't match as XML. When the input data and the specified data match as XML, an assertion exception will be thrown.
Expected XML	Required	Available	Enter the expected XML data.

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 and the specified data match as XML. When the input data and the specified data don't match as XML, an assertion exception will be thrown.

Not match

Verify that the input data and the specified data don't match as XML. When the input data and the specified data match as XML, an assertion exception will be thrown.

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 throw an assertion exception when the order of elements existing in the same path as XML differs. Selected An assertion exception will be thrown when the order of elements existing in the same path as XML differs between the contents of the input data and that of the specified XML data. Not selected (Default) An assertion exception won't be thrown when the order of elements existing in the same path as XML differs between the contents of the input data and that of the specified XML data.

Item name

Required/Optional

Use of variables

Description

Remarks

Raise assertion exception when the order differs

Optional

Not available

Select whether or not to throw an assertion exception when the order of elements existing in the same path as XML differs.

Selected

An assertion exception will be thrown when the order of elements existing in the same path as XML differs between the contents of the input data and that of the specified XML data.

Not selected

(Default)

An assertion exception won't be thrown when the order of elements existing in the same path as XML differs between the contents of the input data and that of 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 connector.

Mass data processing

Mass data processing isn't supported.

Parallel Stream Processing

PSP isn't supported.

Available component variables

Component variable name	Description	Remarks
message_category	When an error occurs, the category of the message code corresponding to the error is stored.	The default value is null.
message_code	When an error occurs, the code of the message code corresponding to the error is stored.	The default value is null.
message_level	When an error occurs, the severity of the message code corresponding to the error is stored.	The default value is null.
error_type	When an error occurs, the error type is stored.	The default value is null. The format of the error type is as follows. Example: java.io.FileNotFoundException
error_message	When an error occurs, the error message is stored.	The default value is null.
error_trace	When an error occurs, the trace information for the error is stored.	The default value is null.

Specification limits

None.

Exception messages

Exception name	Cause	Solution
InputDataNotFoundException	Input data isn't specified.	Specify Input data or draw a data flow.
InvalidPropertyConfigurationException	Expected XML isn't specified.	Specify Expected XML.
AssertionException	Assertion failed.	Check that Input data and Expected XML match or that they don't match.