SchemaValidate Task

From b9421dc80af485591a9c50cc8921f912e0def11e Mon Sep 17 00:00:00 2001 From: Ashlee Young Date: Fri, 23 Oct 2015 10:05:40 -0700 Subject: Removing sources to replace with download links instead. Change-Id: Ie28789a725051aec0d1b04dd291b7690a7898668 Signed-off-by: Ashlee Young --- .../manual/Tasks/schemavalidate.html | 283 --------------------- 1 file changed, 283 deletions(-) delete mode 100644 framework/src/ant/apache-ant-1.9.6/manual/Tasks/schemavalidate.html (limited to 'framework/src/ant/apache-ant-1.9.6/manual/Tasks/schemavalidate.html') diff --git a/framework/src/ant/apache-ant-1.9.6/manual/Tasks/schemavalidate.html b/framework/src/ant/apache-ant-1.9.6/manual/Tasks/schemavalidate.html deleted file mode 100644 index 1aac2ef5..00000000 --- a/framework/src/ant/apache-ant-1.9.6/manual/Tasks/schemavalidate.html +++ /dev/null @@ -1,283 +0,0 @@ - - - - - -SchemaValidate Task - - - - -

SchemaValidate

Description

- -

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

The parser is created validating and namespace aware -
Validation is turned on.
Schema validation is turned on.
Any no-namespace schema URL or file supplied is used as the no-namespace schema -
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 -

<xmlcatalog> elements

<schema> elements, that bind a namespace URI to a URL or a - local filename. -

<dtd> elements which are used to resolve DTDs and entities.

<attribute> elements which are used to set features on the parser. - These can be any number of - http://xml.org/sax/features/ - or other features that your parser may support.

<property> elements, containing string properties -

- -

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

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

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 (defaults to true).	No
file	the file(s) you want to check. (optionally can 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

- -

Nested Elements

- - -

schema

-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	One of url or file is required
file	file of the schema	One of url or file is required

- -

dtd

-<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

xmlcatalog

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

attribute

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: - http://xml.org/sax/features/
-

- - - - - - - - - - - - - - - - -

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

- -

property

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

- - -

Examples

-    <schemavalidate
-      noNamespaceFile="document.xsd"
-      file="xml/endpiece.xml">
-    </schemavalidate>
-

-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">
-      <schemavalidate>
-        <schema namespace="http://schemas.xmlsoap.org/ws/2003/03/addressing"
-          file="${soap.dir}/ws-addressing.xsd" />
-        <schema namespace="http://www.w3.org/2003/05/soap-envelope"
-          file="${soap.dir}/soap12.xsd" />
-        <schema namespace="http://schemas.xmlsoap.org/wsdl/"
-          file="${soap.dir}/wsdl.xsd" />
-        <schema namespace="http://www.w3.org/2001/XMLSchema"
-          file="${soap.dir}/XMLSchema.xsd" />
-        </schemavalidate>
-    </presetdef>
-

-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 -the W3C. -

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

-Use the preset task defined above to validate an XML Schema document. -
- - - - - -- cgit 1.2.3-korg