Setting Web project properties
There are many Web project properties that you can set that affect
the phases in the lifecycle of your project and its dependencies on other
Web resources and Web development processes. You might want to verify or update
these properties after you have updated an existing project or have imported
Web resources into a project .
To view or set Web project properties,
do the following:
Right-click on a Web Project, and from the pop-up menu select
Select a property type in the left pane of the Properties dialog
to view or update properties in the Web project. For each property, you can
apply changes and modify default settings. Based on whether you have a static
or a dynamic Web project, the following property types are available:
- Provides general information about project type, location, and modification
- BeanInfo Path (Dynamic Web project only)
- If you select the Enable Beaninfo Introspection on this project, you can
specify the contents and order of Java™ Bean search paths to provide Bean information
relevant to the project. You can add, remove, and reorder (using the Up and Down buttons)
the packages used to include Bean information.
- Add, remove, or reorder external tools in the build order. When you select New to
create a new external tool to the list, the New External Tool wizard opens,
so that you can define the new build tool.
- Java EE (Dynamic Web project only)
- Identify Web level specification and modify context root and Web content
- Java Build
Path (Dynamic Web project only)
- View or change the information about the Java build path that you supplied when creating
the project using the Create a DynamicWeb Project wizard. Whenever
the Web project is rebuilt, any class files that are created or updated will
be output to the specified output folder.
Note: A library entry on the Java build
path will remain there unless the actual JAR file is deleted from the WEB-INF/lib
folder. If you remove a library path entry but not the JAR file, the library
entry will be re-added to the path automatically.
- Java Compiler
(Dynamic Web project only)
- Define whether to use workspace settings or project setting for compiling Java code,
including settings for Problems, Style, Compliance and Classfiles, and Build
- Javadoc Location (Dynamic Web project only)
- Define a default location (URL) for any Javadoc available to the project.
- Java JAR
Dependencies (Dynamic Web project only)
- Define and reorder JAR dependencies for the project. Note that these dependencies
may differ based on a Web project's association with multiple Enterprise application
- JSP Task Tags
- Add, edit, or remove JSP task tags and assign tag priorities. These "to
do" items appear in your Tasks view.
- JSP Compilation
- Specify when in the build process a JSP should be set to compile
- JSP Fragment (dynamic Web project only)
- Define default encoding, page directive, and content type values for JSP
fragment documents in the web project.
- Links Validation/Refactoring
- Define project-level link management and validation settings. These settings
override corresponding settings in the Workbench Preference settings for the
- Project References
- Reference other Web projects that exist on your workbench workspace.
- Select the server instance used to perform necessary development, test,
and publishing functions for the project.
- Specify which validators should run for the project, and whether validation
should occur automatically when resource updates are written to the project.
The available validators are based on the types of resources in your project.
By default, validators are automatically run when you save resources in a
Web project. If you do not want validators to run automatically when you save
these resources, enable the Override validation preferences
option and disable the Run validation automatically when you save
changes to resources option.
Note: You can also disable automatic
validation (and builds) for all projects by disabling Perform build
automatically on resource modification from the Workbench properties.
If you disable automatic builds, you can manually run a build (and validation)
by selecting .
- Web Content Settings
- Provide any applicable Web content settings for a Web project. You can
specify the document type, CSS profile, and target device.
- Web Project Features
- Select the features you want to be enabled for your Web project, such
as Page Template support.
When you have completed updates to Web project settings, click
save and close the Properties dialog.