PK93886: IF DISPLAY-NAME ATTRIBUTE OF TAG FILE IS DIFFERENT FROM ITS FILENAME, PRECOMPILE JSP OPTION FAILS

Fixes are available

APAR status

Closed as program error.

Error description

If a display-name attribute of tag file is different from the
filename, application deployment with precompile jsp option
fails in V7.0.0.3.

Local fix

Tag name should be the same as the display name.

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server Version    *
*                  7.0 users of tag files.                     *
****************************************************************
* PROBLEM DESCRIPTION: The JSP container fails to compile a    *
*                      tag file when the file name and the     *
*                      display-name attribute value of the     *
*                      tag directive are different.            *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
During the translation phase of a tag file by the JavaServer
Pages (JSP) container an unnecessary check is performed to
ensure the tag file name and the display-name attribute value
in the tag directive match. If these two values do not match,
the following exception is thrown:

jsp W com.ibm.ws.jsp.taglib.TagLibraryCache loadWebInfTagFiles
webinf tagfile failed to scan =[/WEB-INF/tags/sampleTagFile.tag]
com.ibm.ws.jsp.translator.JspTranslationException:
/WEB-INF/tags/sampleTagFile.tag(1,1) \--> JSPG0249E: Tag
directive: illegal to have multiple occurrences of the
attribute "display-name" with different values (old:
sampleTagFile, new: myTagFile)
at
com.ibm.ws.jsp.translator.visitor.tagfilescan.TagFileScanVisitor
.checkConflict(TagFileScanVisitor.java:218)
at
com.ibm.ws.jsp.translator.visitor.tagfilescan.TagFileScanVisitor
.visitTagDirectiveStart(TagFileScanVisitor.java:199)
at
com.ibm.ws.jsp.translator.visitor.JspVisitor.processJspElement(J
spVisitor.java:254)
at
com.ibm.ws.jsp.translator.visitor.JspVisitor.processChildren(Jsp
Visitor.java:420)
at
com.ibm.ws.jsp.translator.visitor.JspVisitor.processJspElement(J
spVisitor.java:234)

In order to cause the above exception the tag file name would
be sampleTagFile.tag and within this tag file would be a tag
directive with a display-name attribute value different from
"sampleTagFile".
For example:
<%@ tag display-name="myTagFile" body-content="empty" %>

Problem conclusion

The JSP Container was modified to allow the display-name
attribute value to be different from the tag file name.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.9.  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
PK93886
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-08-14
Closed date
2009-09-21
Last modified date
2009-09-21

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
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
25 October 2021

Tips

PK93886: IF DISPLAY-NAME ATTRIBUTE OF TAG FILE IS DIFFERENT FROM ITS FILENAME, PRECOMPILE JSP OPTION FAILS

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

R700 PSY

Document Information

Share your feedback

Need support?