WAS v8.5 > Develop applications > Develop web applications > Develop web applications > Develop JSP filesJSP class file generation
At runtime, the WebSphere Application Server JSP engine loads JSP class files from either the WAS temp directory or a web module's WEB-INF/classes directory. The JSP engine first searches for a class file in the temp directory and then it searches in the web module's WEB-INF/classes directory.
In a default installation, the WAS temp directory is typically profile_root/temp.
The batch compiler supports the generation of class files in both the WAS temp directory and a web module's WEB-INF/classes directory, depending on the type of batch compiler target. In addition, the batch compiler enables the generation of class files into any directory on the filesystem, outside of the target application. Generating class files into a web module's WEB-INF/classes directory enables you to deploy the web module as a self-contained WAR file, or a WAR file inside an EAR file.
Batch compiler behavior. Batch compiler behavior when compiling class files
ear.path or war.path supplied enterpriseApp.name supplied compileToDir not supplied; compileToWebInf not supplied, or is true The class files are compiled into the web module's WEB-INF/classes directory. The class files are compiled into the web module's WEB-INF/classes directory. compileToDir not supplied; compileToWebInf is false The class files are compiled into the web module's WEB-INF/classes directory. The class files are compiled into the WAS temp directory, usually profile_root/temp.
compileToDir is supplied; compileToWebInf not supplied, or is either true or false Class files are compiled into compileToDir. Class files are compiled into compileToDir.
Related concepts:
Packages and directories for generated .java and .class files
JSP batch compilation
Global tag libraries (deprecated)
Related
Configure JSP engine parameters
Reference:
Web container configuration for JSP static file access
JSP runtime reloading settings