!--a11y-->
Setting up the Compiler 
You can specify the compiler that is used by the Web Container Service to compile Web applications’ files. You can choose either to use a compiler such as javac (that will execute in a separate process), or to compile a source file by calling the com.sun.tools.javac.Main. You can use the Internal Compiler and External Compiler properties of the Web Container Service to configure the compiler.
...
1. In the Visual Administrator, open the Properties tab of the Web Container Service.
2. Next:
If You Want To |
Then |
Do compiling by calling a method of com.sun.tools.javac.Main |
Set the Internal Compiler property to true.
You need to include the tools.jar JDK library (located in the <JDK_directory>\lib directory) to the classpath of your server process. You can do this using the Config Tool as described in Configuring Cluster Elements. If this library is not present in the server’s classpath, then any attempt of the Web Container service to compile a JSP file using the com.sun.tools.javac.Main results in a java.lang.NoClassDefFoundError exception. |
Use a certain type of Java compiler |
Specify the name of the compiler as a value of the External Compiler property. By default, the container uses javac compiler. You must also set the Internal Compiler property to false. |
3. Choose Update to add it to the list of properties.
4.
Choose
(Save Properties)
after editing the properties to save your settings.
After you have specified the compiler that the Web Container must use, you can enable some of its standard options. If you are using the javac compiler, you can set its option to generate debugging information. You can do this by setting the CompilerDebuggingInfo property of the Web Container Service to true. This is equivalent to using the standard –g option of the javac compiler on the command line.