APAR status |
Closed as program error.
| Error description
When a JSP is compiled via the JSPBatchCompiler script the
java code produced is different from the JSP compiled via the
browser. This sometimes causes a JSP to fail or succeed based
on how file was compiled. Local fixProblem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server 3.5.2 3.5.3 *
* 3.5.4 3.5.5 developers using JSP batch *
* compiler for JSP 1.0. *
****************************************************************
* PROBLEM DESCRIPTION: The generated java code created via *
* the batch compiler differed from *
* the browser generated code. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
JSP Batch Compiler was incorrectly generating java
code due to a bug in the batch compiler. The code
was treating each jsp page as an error page. This
caused the exception handling to be incorrect. Problem conclusion
Modified batch compiler to generate the same code as browser
compiled java code. Temporary fix
//wasdoc0/apars/pq53329/<version>/pq53329_<version>.jar Comments
APAR information | APAR number | PQ53329 | Reported component name | WAS STANDARD NT | Reported component ID | 5648C8301 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2001-10-11 | Closed date | 2001-10-30 | Last modified date | 2001-10-30 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:
Modules/Macros APAR is sysrouted TO one or more of the following:Modules/Macros
|
Fix information |
Fixed component name | WAS STANDARD NT | Fixed component ID | 5648C8301 |
Applicable component levels | R350 PSY | UP |
|