blob: c430e77febd852fa3471c8eaf930f9507ec29de8 [file] [log] [blame]
kprice159fa582006-05-08 21:30:45 +00001<?xml version="1.0" encoding="utf-8"?>
kpriceff280612008-03-03 20:10:12 +00002<!--Arbortext, Inc., 1988-2006, v.4002-->
kprice159fa582006-05-08 21:30:45 +00003<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
4 "..\dtd\concept.dtd">
5<concept id="csrcedt001" xml:lang="en-us">
6<title>Source and batch validation</title>
kprice02ec4b02008-05-14 23:26:58 +00009<keywords><indexterm keyref="cvalidate|1|validationsourcevsbatch" status="changed">validation<indexterm>source
10versus batch</indexterm></indexterm></keywords>
kprice159fa582006-05-08 21:30:45 +000011</metadata></prolog>
13<p>There are two types of validation that can occur when you are working with
14source files in a structured source editor: source validation and batch validation. </p>
15<p>Source validation occurs as you type your code; this validation reflects
16the "unsaved" and "unbuilt" contents of the source you are editing. For example,
17if you were to type the following code in a JSP editor:<lines><codeph>&lt;foo:bar></codeph></lines>where <codeph>foo:bar</codeph>is
18a tag that does not exist, the problem would be discovered immediately and
19would appear underlined in the editor. The advantage of this type of validation
20is that it can alert you to errors instantly.<note>To turn source validation
21on (or off) for all structured text editors, click <menucascade><uicontrol>Window</uicontrol>
23<uicontrol>Structured Text Editors</uicontrol></menucascade> and check (or
24uncheck) <b>Report problems as you type</b>.</note></p>
25<p>Batch validation occurs on saved files. It can catch build process errors
26and other errors that the source validator cannot. For example, suppose you
27typed the following in a JSP editor:<lines>
28<codeph>&lt;%@ taglib uri="" prefix="h"%>
29&lt;%@ taglib uri="" prefix="h"%></codeph></lines>In
30this example, the same prefix is used twice. This would prompt the batch validator
31to trigger markers and to generate build warnings in the Problems view and
32in the Navigator. </p>
33<p>Batch validation can uncover errors in multiple files at once and give
34you a comprehensive view of where problematic code can be found in your project.
35Moreover, you do not need to open files in an editor to run batch validation.
36To run batch validation on specific files, select and right click the files
kpriceff280612008-03-03 20:10:12 +000037in the Project Explorer and then select <menucascade><uicontrol>Validate</uicontrol>
kprice159fa582006-05-08 21:30:45 +000038</menucascade> from the popup menu.</p>
39<note>To set preferences for batch validation, click <menucascade><uicontrol>Window</uicontrol>
43<linkpool type="concept">
44<link href="csrcedt004.dita"><linktext>Structured text editors for markup