You don't need to pull this second schema into Talend it's added automatically through the schemaLocation attribute set in BekwamSales.xsd. The XSD refers to another file hosted on the same server, BekwamCommon.xsd. The input file is also used in the Flow Mode example as the clob contents of a database column. This page has example syntax for isXML().įor a copy of the input file used in the File Mode example, go here.

If you don't have an XSD but want to make sure that you're working with valid XML, consider using a Talend Routine called isXML() that I posted to the Talend Exchange under 'BRules'.

Optionally, route the rejects flow of the tXSDValidator.

Route the main flow of the tXSDValidator.

In the tXSDValidator, set the component to Flow Mode, specify the Input Column, and the XSD file.

Run the source's main flow into the tXSDVallidator component.

Define an input source for the XML like a tAccessInput.

Here is the configuration of the tFilterRow.Īlternatively, tXSDValidator can be used in Flow Mode which will use a Column rather than a local file as an XML source. The logic is implemented as a tFilterRow which routes the result of the 'validate' variable to one of two tJavaRows. This example uses programming logic to query a variable passed out of the tXSDValidator. If you want to simply print out the result of the validation, then check the 'Print to console' checkbox. Two arguments were entered into the Component View: Xsd file and Xml file. This job invokes a tXSDValidator which initiates a flow to a tFilterRow.

The XSD is located on the web and a composed set of data structures a second XSD is imported. A source XML file stored on the local system is validated against an XSD. This blog post presents an example of File mode. TXSDValidator operates in two modes: Flow and File. When a problem arises, you can be assured that what you're producing is expected. If performance is sufficient, this can be a powerful quality check run in the production environment.

In Talend Open Studio, a component called tXSDValidator can be used to compare XML against an XSD. The XSD can also help with system quality by verifying that the XML produced in a data transfer - say the result of a database query - adheres to the agreed-upon format. An XSD serves as a specification, often supporting integration with the development effort through tools like Sparx Systems' Enterprise Architect. An XSD is describes the structure, format, and types of XML. Or, specify 'Flow Mode' to validate a flow-driven Column containing XML. Use the tXSDValidator component to check a local XML file against an XSD.

Xml and xsd validator