|
This document applies only to the following language
version(s):
English |
|
Problem(Abstract) |
JSP fails to compile during Application deployment via
Administrative Console if there is a dependency on another jar file and if
that jar not available on any classpath.
|
|
Symptom |
SystemErr R
com.ibm.websphere.management.exception.AdminException: ADMA0021E: Error in
compiling jsps - xyz.war (rc=1) |
|
Cause |
Dependent jar not available on the JVM classpath |
|
Resolving the
problem |
It is advised to use wsadmin scripting if you want to
Pre-compile jsp during enterprise application deployment. If you want to
use Administrative Console then compile all JSP files before packaging the
application.
Administrative Console:
Add dependent jar to Deployment Manager (in a Cell environment) or
Stand-alone IBM® WebSphere® Application Server classpath.
Use following step to add the dependent jar to classpath.
System Administration -> dmgr > Process Definition > Java™
Virtual Machine
or
System Administration -> server1 > Process Definition > Java
Virtual Machine
in Classpath box, add fully qualified dependant jar file. e.g.
d:/temp/dependent.jar
Save changes.
Restart Deployment Manager or stand-alone Application Server and
Pre-compile jsp will work.
Note: Any jars added to JVM classpath is visible to Application
Server classes and possibly would cause classloader problem. For this
reason, It is advised to remove this dependent jar from JVM classpath to
prevent classloader issues especially if the jar has same name classes as
WebSphere classes. |
|