|
Problem |
Java™ Server Pages (JSP™) Compiler
performance process |
|
|
|
Solution |
JSP process
- WebSphere® Application Server finds the JSP.
- It is converted from the .JSP file format to .Java file format.
This is performed by open source code called JASPER, which is shipped with
WebSphere Application Server. The conversion is done by using TAG
libraries that convert the JSP tags in the .JSP file to Java™ code in the
.Java file.
- The Java compiler is invoked to convert the .Java file to a .class
file.
- The .class file is loaded and run.
Things that affect the performance of the java compile
- Maintenance: Websphere Application Server APARs must be
applied.
PQ71664 WebSphere Application Server Plug-in
PQ72168 WebSphere Application Server J2EE WebContainer
- Jar file structure:
Jar files that do not include the directory structure of the included
files perform poorly; for example, issuing jar cf sample.jar
javax/ejb/*.class builds a poorly-performing jar. Issuing jar cf
sample.jar javax creates a good performing jar.
- Size of the CLASSPATH
When the classloader tries to find a class, it must search each path in
the CLASSPATH starting with the first path through the last path. The
first matching class is loaded. If you have duplicate class files, the
first one found is loaded.
- The number of objects (for example classes, JSP's, and
other Java objects) included in the compilation.
- If you specify the Long branch option on the Java compile,
this lengthens compilation time; however, long branch might be required
when the .Java file is very large. Long branch is not required if you
compile with the Long Branch OFF . If it is required to compile the
program, you receive an error message.
|
|
|
|
|
|
|
|