The following table describes the options parameters available to the WAB utility.
File name of the war file to be transformed into a WAB file. This must be a Servlet 2.3 or 2.4 compliant war file.
Specify the context path for the web application. By default, the base name of the output file is used for the context path. For example, the default context path for inventory.jar is /inventory.
Augment the class path to be used for the JSP file compilation. The WAB utility automatically includes the javax.servlet.* packages on the class path.
-o <output file>
File name of the resulting WAB file. The default name is the base <war file> name with .JAR file extension, placed in the same directory as <war file>.
When specified, the WAB file will include the original JSP source files. By default, JSP files are removed from the WAB, since they are translated to their underlying servlet classes.
When specified, JSP files are compiled with debug information.
Specify the bundle symbolic name. By default, this is the base name of the output file.
Option for translating web archives that are also portlets.
Option for translating web archives that leverage JavaServer Faces technology.
Option for translating web archives that leverage JSP Standard Tag Library.
Option for not adding extension point contribution to lazily start the web project at deployment time.
-javalevel <Java level>
Java compliance level. Valid values are 14, 15, or 16. Default is 15.
A comma separated list of bundle symbolic names to be added to the Require-Bundle header of the manifest file.
A comma separated list of package names to be added to the Import-Package header of the manifest file.
A comma separated list of package names to be added to the Export-Package header of the manifest file.
Specifies the value of Bundle-Version in the manifest file. Default is 1.0.0.
Specifies the bundle activator class to be used as the value of Bundle-Activator in the manifest file. Default will use the standard web bundle activator class.
The version of the runtime which this application is targeting. Valid values are "6.0", "6.1", and "6.1.1". Default is "6.1.1".
This application requires the JWL implementation bundle that does not include a faces configuration. Default is to use JWL with the configuration.
Allows the WAB file to be created even if JSP translation errors are encountered. Useful in situations where it is known that certain JSP errors will not affect the intended use of the web application.
When specified, the WAB file will include the original servlet java classes derived from the JSP files.
Allows the user to specify the JSP compilation level. Options available are "-jsp 20" or "-jsp 21". If nothing is specified, WAB tool compiles JSPs at JSP 2.1 level.