APAR status |
Closed as program error.
| Error description
Two JSPs have DBCS characters. JSP2 is included, either
statically or dynamically, in JSP1. The DBCS characters in JSP1
are displayed properly, while those in JSP2 are not. Local fixProblem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server developers *
* using Double Byte Characters Sets (DBCS) *
* and JSP static includes. *
****************************************************************
* PROBLEM DESCRIPTION: Character encoding for jsp files is *
* incorrect inside of statically *
* included resources. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During reading and parsing of a jsp file, an encoding is
specified to determine the correct encoding used to read the
jsp file. If using a jsp static include, the top level
jsp is not passing the specified character encoding
to the included resources. Problem conclusion
Changed the behavior of the parser to set all statically
included resources character encoding equal to the top
level jsp's character encoding. Temporary fixComments
APAR information | APAR number | PQ57495 | Reported component name | WAS ADVANCED AI | Reported component ID | 5648C8400 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2002-02-04 | Closed date | 2002-02-05 | Last modified date | 2002-02-05 |
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 ADVANCED AI | Fixed component ID | 5648C8400 |
Applicable component levels | R350 PSY | UP |
|