PQ73214: PROBLEMS USING JSP10BATCHCOMPILE.SH WITH WEBSPHERE APPLICATION SERVER V4.01 ON Z/OS | |||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description This apar will address two problems encounterd by the customer when using jsp10BatchCompile.sh with WebSphere Application Server on z/OS. . First, this customer is attempting to precompile using jsp10BatchCompile.sh. They have all of their class files in one jar file which is pointed to by the following statement in their was.conf file: . deployedwebapp.seip.classpath=/pr/seip/class:/pr/seip/class/ external . However when they invoke jsp10BatchCompiler specifying this same classpath, the compile fails because it cannot find the class files located in the jar. To get this to work, they have to point to the jar file in the classpath by specifying the following: . /pr/seip/st1/class/seip.jar:/pr/seip/st1/class/external . Our Planning, Installing, and Using manual states that the webapp-classpath parameter must exactly match the deployedwebapp.<webappname>.classpath property in the was.conf file. Customer feels that the batch compiler should find the JAR file in the classpath the same as the Application server does. . The second problem is that this customer sometimes sees the following warning in his ncf.log: "uses or overrides a deprecated API. Recompile with "-deprecation" for details." He would like to use jsp10BatchCompile.sh to recompile. However the -deprecation option is not supported by the batch compiler. The customer would like to have this support added. This customer is running WebSphere v4.01 with the Plugin.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * version 4.0.1 for z/OS and OS/390 * **************************************************************** * PROBLEM DESCRIPTION: The WebSphere Application Server * * batch compile scripts * * JSP10BATCHCOMPILE.SH and * * JSP11BATCHCOMPILE.SH * * do not recognize the Java compiler * * -deprecation and -verbose options. * * They also do not use JAR files which * * exist in the Web application * * classpath when compiling the JSPs. * **************************************************************** * RECOMMENDATION: * **************************************************************** The JSP level 1.0 and level 1.1 batch compile tools: $was_install_root$/AppServer/bin/JSP10BATCHCOMPILE.SH and $was_install_root$/AppServer/bin/JSP11BATCHCOMPILE.SH do not recognize the -deprecation and -verbose options of the Java compiler. The scripts also do not use JAR files which may exist in the Web application classpath when compiling the JSPs .Problem conclusion The WebSphere Application Server JSP level 1.0 and level 1.1 command line compiler shell scripts are modified to accept and pass to the Java compiler the -verbose and -deprecation flags. Also, if a JAR file is found in the Web application's classpath, that JAR file is included in the classpath passed to the Java compiler. APAR PQ73214 is associated with SERVICE LEVEL W401506 of WebSphere Application Server version 4.0.1 for z/OS and OS/390.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: PQ73335 Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 401
Software edition:
Reference #: PQ73214
IBM Group: Software Group
Modified date: Jun 5, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.