APAR status
Closed as program error.
Error description
A customer using a custom tag (urn:jsptagdir) started to see
problems when upgrading from WAS 5.0.2.0 to 5.0.2.6. These
errors were Jasper errors.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server users *
****************************************************************
* PROBLEM DESCRIPTION: Some custom tags fail after
PQ83860 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
sSome custom tag throw "org.apache.jasper.JasperException: This
absolute uri *** cannot be resolved in either web.xml or the
jar files deployed with this application"
Problem conclusion
Implemented a new way to find the user URI in the custom tag
Temporary fix Comments
APAR information |
APAR number |
PQ91680 |
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-07-20 |
Closed date |
2004-08-25 |
Last modified date |
2004-08-25 |
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 |
|