Format of the build specification file for .jsp files

The Klocwork build specification for .jsp files is a semi-colon-separated text file generated by kwwebappscan containing the following information:

• optional application server settings, identified in jspconfig lines
• the web applications to analyze, identified in jspcompile lines

This information is repeated for each web application in the project. For example:

version;108jspconfig;config1;appserver.name=tomcat_6_0;appserver.location=d:\test\tomcat_6.0.14 jspcompile;config1;D:\test\webgoat.war.unpacked

The first field of each line is a tag to identify the type of line. The possible tags are as follows:

version line

The version line is used to define the build specification format version. It must be the first line in the build specification. Only one version line may appear in a build specification.

Example version line:

version;108

Version 1.4 or later indicates that the build specification was generated using a source encoding of UTF-8, allowing multibyte characters (for example, Japanese). To ensure that kwbuildproject processes the build specification with UTF-8 encoding, the version must be version;104 or later.

jspconfig line

The jspconfig line is used to identify a non-default application server. If no application server was specified in the kwwebappscan command line, the jspconfig line will look like this:

jspconfig;config1

Example jspconfig line where a non-default application server was specified in the kwwebappscan command line:

jspconfig;config1;appserver.name=tomcat_6_0;appserver.location=d:\test\tomcat_6.0.14

The fields are:

jspcompile line

Each jspcompile line is used to point to one web application.

Example jspcompile line:

jspcompile;config1;D:\test\webgoat.war.unpacked

The fields are: