Fixes are available
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
APAR status
Closed as program error.
Error description
When calling a JSP which uses a tag containing another tag with deferred-attributes, a 500 error message page is delivered due to a com.ibm.ws.jsp.translator.JspTranslationException.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server Full * * Profile versions 7.0, 8.0, and 8.5.5 and * * Liberty Profile version 8.5.5 users of * * JavaServer Pages (JSP). * **************************************************************** * PROBLEM DESCRIPTION: Using a JSP tag with dynamic * * attributes using the * * prefix:attributeName format generates * * the following translation error: * * JSPG0227E: Exception caught while * * translating /test.jsp: JSPG0299E: The * * dynamic attribute * * prefix:attributeName has a prefix * * that does not map to a namespace. * **************************************************************** * RECOMMENDATION: * **************************************************************** A JSP page in standard and document format that declare a namespace and uses this as the prefix of a dynamic attribute in a JSP tag causes a JSP translation error. A namespace can be declared using the JSP taglib directive or using the xmlns prefix in JSP files in standard and document form, respectively; however, either type of declaration originates the following exception when using the fully qualified name dynamic attribute: com.ibm.ws.jsp.translator.JspTranslationException: JSPG0227E: Exception caught while translating /test.jsp: JSPG0299E: The dynamic attribute prefix:attributeName has a prefix that does not map to a namespace. at com.ibm.ws.jsp.translator.visitor.generator.BaseTagGenerator.gen erateSetters(BaseTagGenerator.java:287) ... The following example will produce the issue: <%@ taglib prefix="dynamicAttributes" uri="/dynamicAttributes" %> <%@ taglib prefix="test" uri="/test" %> <html> <head> <title>PI43036</title> </head> <body> <dynamicAttributes:simpleTag test:dynamicAttributeName="This will fail." /> </body> </html>
Problem conclusion
The JSP container was modified to register the namespaces accordingly to resolve the JSPG0299E error. The fix for this APAR is currently targeted for inclusion in fix packs 8.0.0.12 and 8.5.5.8. 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
PI43036
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-06-15
Closed date
2015-08-11
Last modified date
2015-08-11
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
R700 PSY
UP
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
11 January 2022