The WAB utility is invoked through a script. On Windows® systems, this script is wab.bat
. On Linux® systems this script is wabc
. The following will use the Windows wab.bat
script in examples, and assumes that the WAB utility directory has been added to the system's PATH environment.
The WAB utility performs the following transformations on your web application:
- All JSP files are translated to their underlying servlet classes. In addition to the standard J2SE libraries, the utility automatically adds required javax.servlet* class libraries to the class path during translation. Any other classes referenced by the application's JSPs, that are not part of the application itself (through WEB-INF/classes or WEB-INF/lib), must be specified through the utility's –classpath parameter.
- If an OSGi compliant manifest file does not exist in the web application, one will be added. It will have the necessary package dependency statements for supporting web applications. If your application is referencing additional external packages, you will need to include your own custom META-INF/MANIFEST.MF manifest file that includes these package dependencies through either the Import-Package or Require-Bundle fields, or use the -requirebundle parameter to add them to the Require-Bundle field. Note that the utility will augment an existing manifest file to contain any missing dependencies, and will not overwrite any preexisting entries.
- A plugin.xml file will be created by default to contain the extension point contribution to lazily start the web application. If you use the WAB tool with -nolazystart option, the plugin.xml file will not be created.
Parent topic: WAB Utility: XPD622