Java Reference
In-Depth Information
Figure 11.2 The J2EE Build Settings panel lets you set whether to use Jasper for JSP
validation, options around the J2EE deployment (which can occur as a JAR or as an exploded
directory), and whether to perform builds when the frame is deactivated.
Jasper, a
JSP
compiler that comes bundled with the Jakarta Tomcat servlet con-
tainer, is fully integrated into
IDEA
. It's used to validate
JSP
s against the specifica-
tion and report any errors found, ensuring a higher standard of quality and
compliance in your code. If you enable the
Run Jasper validator for
JSP
files
checkbox,
IDEA
will run Jasper each time the web application is built. Alterna-
tively, you can choose to not validate your
JSP
s or to selectively validate them by
hand using the context menu when editing a
JSP
.
Web applications can be deployed to a web application server in two ways: as a
WAR
file (a single archive containing a directory structure) or as a simple directory
structure that hasn't been packaged into an archive file. This latter format is
referred to as an
exploded
WAR
file
(or exploded directory) because it represents
the contents of a
WAR
if it was un-archived and expanded onto the file system.
The
J2EE
Build Settings
tab lets you specify which of these two deployable for-
mats is produced when the
IDE
builds the web module.
You can tell
IDEA
to produce neither deployable format by disabling
both checkboxes, but
IDEA
will be unable to deploy your web application
to the web application server if you do so.
WARNING
