Follow Techotopia on Twitter

On-line Guides
All Guides
eBook Store
iOS / Android
Linux for Beginners
Office Productivity
Linux Installation
Linux Security
Linux Utilities
Linux Virtualization
Linux Kernel
System/Network Admin
Programming
Scripting Languages
Development Tools
Web Development
GUI Toolkits/Desktop
Databases
Mail Systems
openSolaris
Eclipse Documentation
Techotopia.com
Virtuatopia.com
Answertopia.com

How To Guides
Virtualization
General System Admin
Linux Security
Linux Filesystems
Web Servers
Graphics & Desktop
PC Hardware
Windows
Problem Solutions
Privacy Policy

  




 

 

Eclipse Web Tools Guide
Previous Page Home Next Page

Source and batch validation

There are two types of validation that can occur when you are working with source files in a structured source editor: source validation and batch validation.

Source validation occurs as you type your code; this validation reflects the "unsaved" and "unbuilt" contents of the source you are editing. For example, if you were to type the following code in a JSP editor:

<foo:bar>

where foo:baris a tag that does not exist, the problem would be discovered immediately and would appear underlined in the editor. The advantage of this type of validation is that it can alert you to errors instantly.
Note: To turn source validation on (or off) for all structured text editors, click Window > Preferences > General > Editors > Structured Text Editors and check (or uncheck) Report problems as you type.
Batch validation occurs on saved files. It can catch build process errors and other errors that the source validator cannot. For example, suppose you typed the following in a JSP editor:


<%@ taglib uri="https://java.sun.com/jsf/html" prefix="h"%>
<%@ taglib uri="https://java.sun.com/jsf/html" prefix="h"%>

In this example, the same prefix is used twice. This would prompt the batch validator to trigger markers and to generate build warnings in the Problems view and in the Navigator.

Batch validation can uncover errors in multiple files at once and give you a comprehensive view of where problematic code can be found in your project. Moreover, you do not need to open files in an editor to run batch validation. To run batch validation on specific files, select and right click the files in the Project Explorer and then select Validate from the popup menu.

Note: To set preferences for batch validation, click Window > Preferences > Validation

 
 
  Published under the terms of the Eclipse Public License Version 1.0 ("EPL") Design by Interspire