blob: 5b6b807ff6abf336d505c8db2463c89c5a2406db [file] [log] [blame]
kprice159fa582006-05-08 21:30:45 +00001<?xml version="1.0" encoding="utf-8"?>
kprice4873f982007-04-05 03:39:40 +00002<!--Arbortext, Inc., 1988-2006, v.4002-->
kprice647b7352006-05-17 21:27:16 +00003<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
4 "task.dtd">
kprice159fa582006-05-08 21:30:45 +00005<task id="tvdtschm" xml:lang="en-us">
6<title>Validating XML schemas</title>
7<titlealts>
8<searchtitle>Validating XML schemas</searchtitle>
9</titlealts>
10<shortdesc>Validating an XML schema determines whether the current state of
11the XML schema file is semantically valid. Any errors will be displayed in
12the Problems view.</shortdesc>
13<prolog><metadata>
14<keywords><indexterm>XML schema files<indexterm>validating</indexterm></indexterm>
15</keywords>
16</metadata></prolog>
17<taskbody>
18<context><p>The following instructions were written for the Resource perspective,
19but they will also work in many other perspectives.</p><p>To validate an XML
kpricede20a692008-04-24 00:27:47 +000020schema, complete the following steps:</p></context>
kprice159fa582006-05-08 21:30:45 +000021<steps>
kprice4873f982007-04-05 03:39:40 +000022<step><cmd>Right-click your file in the Navigator view and click <uicontrol>Validate</uicontrol>.</cmd>
23</step>
kprice159fa582006-05-08 21:30:45 +000024<step><cmd> If validation was not successful, you can refer to the Problems
kpricede20a692008-04-24 00:27:47 +000025view to see what problems were logged. </cmd><info> <note> If you receive
26an error message indicating that the Problems view is full, you can increase
27the number of error messages allowed by clicking <menucascade><uicontrol>Window</uicontrol>
28<uicontrol>Preferences</uicontrol></menucascade> and selecting <menucascade>
29<uicontrol>General</uicontrol><uicontrol>Markers</uicontrol></menucascade>.
30Select the <uicontrol>Use marker limits</uicontrol> check box and change the
31number in the <uicontrol>Limit visible items per group</uicontrol> field.</note></info>
32</step>
kprice159fa582006-05-08 21:30:45 +000033</steps>
34<result><p>The XML schema support in the XML schema editor is based on the
35W3C XML Schema Recommendation Specification. The XML Schema specifications
36XML Schema Part 1: Structures and XML Schema Part 2: Datatypes from the W3C
37Web site are used for validation.</p><p>Certain error messages contain a reference
38to the schema constraints listed in Appendix C of the XML Schema Part 1: Structures
39document. Each constraint has a unique name that will be referenced in the
kpricede20a692008-04-24 00:27:47 +000040error message. For example, if you receive an error message with this text: <systemoutput>ct-props-correct</systemoutput> and
41you searched in the Structure document for the text, you would find that it
42is for the section "Schema Component Constraint: Complex Type Definition Properties
43Correct". </p><p>You can set up a project's properties so that different types
44of project resources are automatically validated when you save them (this
45is set for all resources <?Pub Caret?>by default). From a project's pop-up
46menu select <uicontrol>Properties</uicontrol>, then select <uicontrol>Validation</uicontrol>.
47Any validators you can run against your project will be listed in the Validation
48page.</p></result>
kprice159fa582006-05-08 21:30:45 +000049</taskbody>
50<related-links>
51<link href="../../org.eclipse.jst.j2ee.doc.user/topics/tjval.dita" scope="peer">
52<desc>General validation information</desc>
53</link>
54<link href="http://www.w3.org/TR/xmlschema-1" scope="external"><linktext>XML
55Schema Part 1: Structures</linktext>
56<desc>See the W3C Web site for more information on XML Schema specifications</desc>
57</link>
58<link href="http://www.w3.org/TR/xmlschema-2" scope="external"><linktext>XML
59Schema Part 2: Datatypes</linktext>
60<desc>See the W3C Web site for more information on XML Schema specifications</desc>
61</link>
62</related-links>
63</task>
kpricede20a692008-04-24 00:27:47 +000064<?Pub *0000003403?>