Building JSP targets

The build phase for a JSP target:

Provides link verification
Creates the Jaguar.properties and Database.properties files from current EAServer and database profiles, and places them in the target Web-Inf\classes directory
Moves the files to a Build folder under the target folder to make the files available for deployment

You can build an entire JSP target, or just one file. Building a file lets you quickly make sure that links from the file work.

Link verification

When the build process verifies the links from one file to another in the target, it displays information about broken links in the Output window. It also verifies the syntax—but not the integrity—of links outside the target.

Double-clicking the broken link in the Output window opens the file in the HTML Editor. You can choose to fix the link or not. If you do not fix the link, the deployed files will also have a broken link.

The Web target processes the following HTML attributes during link verification:

ACTION	CODEBASE	HTTP-EQUIV
BACKGROUND	DYNSRC	SRC
CODE	HREF

Elements that use these attributes include:

**Table 12-1: HTML elements parsed for link integrity**
Element	Attributes processed
A	HREF
Applet	CODE, CODEBASE
Base	HREF
Bgsound	SRC
Body	BACKGROUND
Form	ACTION
Frame	SRC
Img	SRC, DYNSRC
Input	SRC (for TYPE="image")
IsIndex	ACTION
Layer	SRC, BACKGROUND
Link	HREF
Meta	HTTP-EQUIV
Script	SRC
Object	CODE, CODEBASE
Table	BACKGROUND
TD	BACKGROUND
TH	BACKGROUND

Files in Build folder

The JSP target build process copies files from the target Source folder to the target Build folder. These folders are visible in the JSP target development environment (in the Library painter or in the System Tree when the root is set to My Computer).

Files from the Build folder are processed during deployment to a Web site. When you explicitly build a target, you can choose to build all of the files in the target, or only those files that have changed since the last build.

How to build a JSP target

Invoking the build process whenever you save a file gives you timely information about the links in the file, and ensures that you have a copy of your changes in the Build folder, ready for deployment. You can also build a file or an entire target at any time.

**Table 12-2: Build selection options**
Select this menu item	To do this
Full Build	Build all the files in the target and regenerate the Jaguar.properties and Database.properties files
Incremental Build	Build target files that have changed since the last build

To build a JSP target:

On the Workspace tab page of the System Tree, right-click a JSP target and select Full Build or Incremental Build from the pop-up menu.

You can also set a deployment option to specify if you want to do a full build or incremental build when you deploy your JSP target. You must do a full build to make sure connection properties for new database or EAServer profiles are available to a JSP target. For information on setting this option, see “Editing a JSP deployment configuration”.

If you want to build all of the files within a workspace, you can use the workspace Run menu. When you build a workspace, the build processes target files within the active workspace. A workspace build can also be full or incremental.

To build an individual file:

On the Workspace tab page of the System Tree, right-click a file, then select Build from the pop-up menu.

To build multiple files (without building a target or workspace):

In the List view of the Library painter, display the Source directory under your JSP target directory.
Use the ctrl key to select all the files you want to build.

You can use the shift key instead to select consecutive files in the list.
Right-click the selected files and select Build from the pop-up menu.