PQ58795, 4.0: Empty strings as the attribute value
for custom tags
Downloadable files
Abstract
Custom tags are created in a .tld file. In a JavaServerâ„¢
Pages (JSP), an empty string value is used as the attribute value of a
custom tag. This causes a JSP error.
Download Description
PQ58795 resolves the following problem:
Custom tags are created in a .tld file. In a JSP, an empty string value is
used as the attribute value of a custom tag. This causes the message JSP
error "unable to convert to string class name ={attribute type} attribute
= {attribute name}" to be displayed on the browser. On WebSphere®
Application Server V4.0 releases without PQ57258, the result is
java.lang.Error: Fatal Error: missing resource.
USERS AFFECTED:
WebSphere Application Server developers using JSP with custom tags.
PROBLEM DESCRIPTION:
WebSphere Application Server returns an error message "unable to convert
string" when custom tag attribute value is set to an empty String object.
RECOMMENDATION:
WebSphere Application Server JSP processor is unable to process a custom
tag attribute containing an empty string for a value. This is working
according to the specification. However, this is a behavior change
introduced while implementing performance improvements for custom tag
libraries.
PROBLEM CONCLUSION:
Since this was a change in behavior, backwards compatibility is provided
for existing customers. WebSphere Application Server code was modified to
permit existing JSP containing custom tags with empty values to execute
while maintaining the performance improvements that were introduced.
This can be corrected by not using an empty string as an attribute value
for a custom tag.
Prerequisites
None
Installation Instructions
Please refer to the readme.txt for installation instructions.