PM03123: THE JSP ENGINE FAILS TO RESOLVE TLD IMPORT STATEMENTS

Fixes are available

APAR status

Closed as program error.

Error description

Problem Description

The JavaServer Pages (JSP) engine fails to resolve Tag Library
Descriptor (TLD) import statements when the TLD is packed
inside a jar file contained in a classpath container that is
deployed to WebSphere Application Server by selecting it as a
Web Library under JEE Module dependencies.

WebSphere Application Server 6.1

Local fix

Copy the referenced .tld file and copy it to the web/WEB-INF/lib
folder

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server version    *
*                  6.1 and 7.0 users                           *
****************************************************************
* PROBLEM DESCRIPTION: Tag Library Descriptor (TLD) files,     *
*                      which are packaged in a jar file, are   *
*                      not found in a loose library            *
*                      configuration environment.              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Rational Application Developer allows a loose library
configuration setting (that is, some of the files or libraries
are not deployed on the WebSphere Application Server).  When
TLD files are packaged in a jar and deployed in this type of
environment, WebSphere Application Server cannot locate and
load the TLD files.

Problem conclusion

The JSP Container code was modified to load the TLD files from
a jar in a loose library configuration environment.

The fix for this APAR is currently targeted for inclusion in
fixpacks 6.1.0.31 and 7.0.0.11
Please refer to the recommended updates page for delivery
information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PM03123
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-12-09
Closed date
2010-01-29
Last modified date
2010-01-29

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PM03123: THE JSP ENGINE FAILS TO RESOLVE TLD IMPORT STATEMENTS

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?