This schemavalidate task validates XML files described by an XML Schema. The task extends the XmlValidate task with XSD-specific features.

  1. The parser is created validating and namespace aware.
  2. Validation is turned on.
  3. Schema validation is turned on.
  4. Any no-namespace schema URL or file supplied is used as the no-namespace schema.
  5. All nested schema declarations are turned into the list of namespace-url bindings for schema lookup.

Note that nested catalogs are still used for lookup of the URLs given as the sources of schema documents, so you can still delegate lookup to a catalog, you just need to list all schema URIs and their URL equivalents.

This task supports the use of nested

The task only supports SAX2 or later parsers: it is an error to specify a SAX1 parser.


Attribute Description Required
classname the parser to use. No
classpathref where to find the parser class. Optionally can use an embedded <classpath> element. No
disableDTD Flag to disable DTD support. DTD support is needed to validate XSD files themselves, amongst others. No; default false
failonerror fails on a error if set to true. No; defaults to true
file the file(s) you want to check (optionally use an embedded fileset). No
fullchecking enable full schema checking. Slow but strict. No; default true
lenient if true, only check the XML document is well formed No
noNamespaceFile filename of a no-namespace XSD file to provide the schema for no-namespace XML content No
noNamespaceURL URL of a no-namespace XSD file to provide the schema for no-namespace XML content No
warn log parser warn events No

Parameters specified as nested elements


Identify the name and location of a schema that may be used in validating the document(s).

Attribute Description Required
namespace URI of the schema namespace Yes
url URL of the schema Exactly one of the two
file file of the schema


<dtd> is used to specify different locations for DTD resolution.

Attribute Description Required
publicId Public ID of the DTD to resolve Yes
location Location of the DTD to use, which can be a file, a resource, or a URL Yes


The <xmlcatalog> element is used to perform entity resolution.


The <attribute> element is used to set parser features.
Features usable with the Xerces parser are defined here: Setting features
SAX features are defined here:

Attribute Description Required
name The name of the feature Yes
value The boolean value of the feature Yes


The <property> element is used to set properties. These properties are defined here for the Xerces XML parser implementation: XML Parser properties. Properties can be used to set the schema used to validate the XML file.

Attribute Description Required
name The name of the feature Yes
value The string value of the property Yes


<schemavalidate noNamespaceFile="document.xsd"

Validate a document against an XML schema. The document does not declare any schema itself, which is why the noNamespaceFile is needed.

<presetdef name="validate-soap">
    <schema namespace=""
    <schema namespace=""
    <schema namespace=""
    <schema namespace=""

Declare a new preset task, <validate-soap>, that validates XSD and WSDL documents against the relevant specifications. To validate XSD documents, you also need XMLSchema.dtd and datatypes.dtd in the same directory as XMLSchema.xsd, or pointed to via the catalog. All these files can be fetched from W3C.

<validate-soap file="xml/test.xsd"/>

Use the preset task defined above to validate an XML Schema document.