blob: 1adfec277b9727f9d368d66a87cf0120e506afdb [file] [log] [blame]
kpriceef160682006-08-29 18:08:31 +00001<?xml version="1.0" encoding="utf-8"?>
kprice8ca223b2007-04-05 03:35:57 +00002<!--Arbortext, Inc., 1988-2006, v.4002-->
3<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
4 "task.dtd">
kpriceef160682006-08-29 18:08:31 +00005<task id="twxvalid" xml:lang="en-us">
6<title>Validating XML files</title>
7<titlealts>
8<searchtitle>Validating XML files</searchtitle>
9</titlealts>
10<shortdesc>When you validate your XML file, the XML validator will check to
11see that your file is valid and well-formed.</shortdesc>
12<prolog><metadata>
13<keywords><indexterm>XML files<indexterm>validating</indexterm></indexterm>
14</keywords>
15</metadata></prolog>
16<taskbody>
17<context><p>The XML editor will process XML files that are invalid or not
18well-formed. The editor uses heuristics to open a file using the best interpretation
19of the tagging that it can. For example, an element with a missing end tag
20is simply assumed to end at the end of the document. As you make updates to
21a file, the editor incrementally reinterprets your document, changing the
22highlighting, tree view, and so on. Many formation errors are easy to spot
23in the syntax highlighting, so you can easily correct obvious errors on-the-fly.
24However, there will be other cases when it will be beneficial to perform formal
kpriceb59c9f62008-04-02 21:24:37 +000025validation on your documents.</p><p>You can validate your file by selecting
26it in the Navigator view, right-clicking it, and clicking <uicontrol>Validate</uicontrol>.
27Any validation problems are indicated in the Problems view. You can double-click
28on individual errors, and you will be taken to the invalid tag in the file,
29so that you can make corrections.</p></context>
30<postreq><note> If you receive an error message indicating that the Problems
31view is full, you can increase the number of error messages allowed by clicking <menucascade>
32<uicontrol>Window</uicontrol><uicontrol>Preferences</uicontrol></menucascade> and
33selecting <menucascade><uicontrol>General</uicontrol><uicontrol>Markers</uicontrol>
34</menucascade>. Select the <uicontrol>Use marker limits</uicontrol> check
35box and change the number in the <uicontrol>Limit visible items per group</uicontrol> <?Pub Caret?>field.</note><p>You
36can set up a project's properties so that different types of project resources
37are automatically validated when you save them. From a project's pop-up menu,
38click <uicontrol>Properties</uicontrol>, then select <uicontrol>Validation</uicontrol>.
kpriceef160682006-08-29 18:08:31 +000039Any validators you can run against your project will be listed in the Validation
40page.</p></postreq>
41</taskbody>
42<related-links>
43<link href="../../org.eclipse.jst.j2ee.doc.user/topics/tjval.dita" scope="peer">
kprice38ea4e12007-04-05 03:22:56 +000044<linktext>Validating code in enterprise applications</linktext></link>
kpriceef160682006-08-29 18:08:31 +000045</related-links>
46</task>
kpriceb59c9f62008-04-02 21:24:37 +000047<?Pub *0000002658?>