Skip to main content Skip to complementary content

tDTDValidator Standard properties

These properties are used to configure tDTDValidator running in the Standard Job framework.

The Standard tDTDValidator component belongs to the XML family.

The component in this framework is available in all Talend products.

Basic settings

Schema and Edit Schema

A schema is a row description, it defines the number of fields to be processed and passed on to the next component.

The schema of this component is read-only. It contains standard information regarding the file validation.

DTD file

Filepath to the reference DTD file.

XML file

Filepath to the XML file to be validated.

If XML is valid, display If XML is invalid, display

Type in a message to be displayed in the Run console based on the result of the comparison.

Print to console

Select this check box to display the validation message.

Advanced settings

tStatCatcher Statistics

Select this check box to gather the processing metadata at the Job level as well as at each component level.

Global Variables

Global Variables

ERROR_MESSAGE: the error message generated by the component when an error occurs. This is an After variable and it returns a string. This variable functions only if the Die on error check box is cleared, if the component has this check box.

DIFFERENCE: the result of the validation. This is a Flow variable and it returns a string.

VALID: the validation result. This is a Flow variable and it returns a Boolean.

A Flow variable functions during the execution of a component while an After variable functions after the execution of the component.

To fill up a field or expression with a variable, press Ctrl+Space to access the variable list and choose the variable to use from it.

For more information about variables, see Using contexts and variables.

Usage

Usage rule

This component can be used as standalone component but it is usually linked to an output component to gather the log data.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!