JSP
files are usually compiled the first time they are displayed on the server.
Setting the preferences to compile the JSP files when a project is built in
the workspace can improve performance, since the server will not need to compile
the JSP files initially.
Precompiled JSP files will be included in the WEB-INF/classes directory
of the Web project. The JSP processor on the server will use these classes
rather than compiling. You can also set the debug option when compiling the
JSP files. Use this option if you plan to debug JSP files on the server. You
can specify when JSP files are compiled on the preferences page ().
Restriction: The debug option is only supported for IBM® WebSphere® Application
Servers.
You can validate the code in your JSP file by right-clicking
on a JSP page in the Project Explorer and selecting Validate.
The JSP Validator uses existing WebSphere technology to validate JSP
files in a project by translating them into the corresponding Java™ code
and then checking the Java code for compile errors.
Note: If
you compile a JSP using JAR files that have been compiled with Java V1.4,
you will get an error similar to the following:
JavaCompile: cannot access SpeciesSpeciesIDBean; bad class file
D:\...\WEB-INF\classes\...\SpeciesSpeciesIDBean.class;
class file has wrong version 48.0, should be 47.0;
please remove or make sure it appears in the correct subdirectory of the classpath.