kprice | ef16068 | 2006-08-29 18:08:31 +0000 | [diff] [blame] | 1 | <?xml version="1.0" encoding="utf-8"?>
|
kprice | 8ca223b | 2007-04-05 03:35:57 +0000 | [diff] [blame] | 2 | <!--Arbortext, Inc., 1988-2006, v.4002-->
|
| 3 | <!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
|
| 4 | "task.dtd">
|
kprice | ef16068 | 2006-08-29 18:08:31 +0000 | [diff] [blame] | 5 | <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
|
| 11 | see 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
|
| 18 | well-formed. The editor uses heuristics to open a file using the best interpretation
|
| 19 | of the tagging that it can. For example, an element with a missing end tag
|
| 20 | is simply assumed to end at the end of the document. As you make updates to
|
| 21 | a file, the editor incrementally reinterprets your document, changing the
|
| 22 | highlighting, tree view, and so on. Many formation errors are easy to spot
|
| 23 | in the syntax highlighting, so you can easily correct obvious errors on-the-fly.
|
| 24 | However, there will be other cases when it will be beneficial to perform formal
|
kprice | b59c9f6 | 2008-04-02 21:24:37 +0000 | [diff] [blame] | 25 | validation on your documents.</p><p>You can validate your file by selecting
|
| 26 | it in the Navigator view, right-clicking it, and clicking <uicontrol>Validate</uicontrol>.
|
| 27 | Any validation problems are indicated in the Problems view. You can double-click
|
| 28 | on individual errors, and you will be taken to the invalid tag in the file,
|
| 29 | so that you can make corrections.</p></context>
|
| 30 | <postreq><note> If you receive an error message indicating that the Problems
|
| 31 | view is full, you can increase the number of error messages allowed by clicking <menucascade>
|
| 32 | <uicontrol>Window</uicontrol><uicontrol>Preferences</uicontrol></menucascade> and
|
| 33 | selecting <menucascade><uicontrol>General</uicontrol><uicontrol>Markers</uicontrol>
|
| 34 | </menucascade>. Select the <uicontrol>Use marker limits</uicontrol> check
|
| 35 | box and change the number in the <uicontrol>Limit visible items per group</uicontrol> <?Pub Caret?>field.</note><p>You
|
| 36 | can set up a project's properties so that different types of project resources
|
| 37 | are automatically validated when you save them. From a project's pop-up menu,
|
| 38 | click <uicontrol>Properties</uicontrol>, then select <uicontrol>Validation</uicontrol>.
|
kprice | ef16068 | 2006-08-29 18:08:31 +0000 | [diff] [blame] | 39 | Any validators you can run against your project will be listed in the Validation
|
| 40 | page.</p></postreq>
|
| 41 | </taskbody>
|
| 42 | <related-links>
|
| 43 | <link href="../../org.eclipse.jst.j2ee.doc.user/topics/tjval.dita" scope="peer">
|
kprice | 38ea4e1 | 2007-04-05 03:22:56 +0000 | [diff] [blame] | 44 | <linktext>Validating code in enterprise applications</linktext></link>
|
kprice | ef16068 | 2006-08-29 18:08:31 +0000 | [diff] [blame] | 45 | </related-links>
|
| 46 | </task>
|
kprice | b59c9f6 | 2008-04-02 21:24:37 +0000 | [diff] [blame] | 47 | <?Pub *0000002658?>
|