APAR status
Closed as program error.
Error description
When using WSAD and accessing a jsp whose tld location is specif
ied in web.xml, application server will load the jsp for first
time. But if the jsp is modified later, application server will
fail to locate the tld file.
Following error message will occur while accessing a modified
jsp:
Error 500: File "D:/IBM/wsappdev51/sqlj2/MyTagsJavaProject/META-
INF/taglib.tld" not found
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server users *
****************************************************************
* PROBLEM DESCRIPTION: If WebSphere Application Server users *
* use loose jar support for TLD, it may *
* fail *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Application Server loose jar support does not always return the
right path for the TLD in the jar file.
Problem conclusion
Implement a new algorithm to ensure WebSphere Application
Server always finds the TLD in the loose jar
Temporary fix Comments
APAR information |
APAR number |
PQ88203 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00W |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-04-29 |
Closed date |
2004-05-06 |
Last modified date |
2004-05-06 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|