Validation(XML Schema)

Operation Name

Validation (XML Schema)

Function overview

Verifies validity of XML Schema.

Data Model

Data model of this component is XML type.
Refer to "Schema" for input/output schema.

Properties

For information about using variables, refer to "variables".
Basic settings
Item name Required/Optional Use of Variables Description Remarks
Name Required Not available Input the name on the script canvas.  
Input data Required Not available Select the component on the script canvas.  
Required settings
Item name Required/Optional Use of Variables Description Remarks
Validation file Required Available Enter the XML Schema file.

Click [Browse] button to activate the file Selectr and Select the file.
  • Specify the absolute path on the server OS local file system.
Maximum number of error reports Optional Available Enter the maximum number of error reporting when validation fails.
  • Available value is "1" to "2147483646".
  • The default is "1000".
Data processing method
Item name Required/Optional Use of Variables Description Remarks
Mass data processing Required Not available Select a data processing method.
  • [Use script settings]: (default)
    Apply mass data processing settings of script property to adapter.
  • [Disable]:
    Mass data processing is not performed.
  • [Enable]:
    Mass data processing is performed.
  
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.		  

Schema

The same as the schema of the input source component.

Mass Data Processing

Mass data processing is supported.

PSP Usage

PSP is not supported.

Available component variables

Component variable name Description Remarks
success Returns the outcome of treatment.
  • The value defaults to null.
  • True if the operation successes, false when the operation fails.
message_category Stroes the category to which corresponding message code belongs to, when an error occurs.
  • The value defaults to null.
message_code Stores its corresponding message code of occured error.
  • The value defaults to null.
message_level Stores the severity of the corresponding message code of the occured error.
  • The value defaults to null.
error_type Stores the type of the occured error.
  • The value defaults to null.
  • Error is represented in the format depicted below.
    Example:java.io.FileNotFoundException
  • The message may vary depending on DataSpider Servista version.
error_message Stores the error message for the occured error.
  • The value defaults to null.
  • The message may vary depending on DataSpider Servista version.
error_trace Stores stack trace of the occurred error.
  • The value defaults to null.
  • The message may vary depending on DataSpider Servista version or the client application used.

Specification Limits

None.

Main exceptions

Exception name Cause Solution
InputDataNotFoundException [Input data] is not specified. Specify the [Input data], or draw the data flow.
InvalidPropertyConfigurationException [Validation file] is not specified. Specify [Validation file].
ValidationException [Input data] is not valid for the XML Schema specified [Validation file]. Input [Input data] valid data XML Schema specified [Validation file].
java.io.FileNotFoundException File specified in [Validation file] does not exist. Check the specified file.