APAR status
Closed as program error.
Error description
THIS JSP CODE WORKS!
<%
PortletURL _toto = renderResponse.createActionURL();
_toto.setWindowState(new WindowState("Maximized"));
_toto.setPortletMode(new PortletMode("Edit"));
_toto.setSecure(false);
_toto.setParameter("myParam","testParam");
%>
<i><%=_toto%>
THIS JSP CODE DOES NOT WORK!
<portlet:actionURL windowState="Maximized" portletMode="Edit"
secure="False" var="toto">
<portlet:param name="myParam" value="testParam"/>
</portlet:actionURL>
<i><%=toto%> <!-- this code prints null here -->
I can make the following observations about differences between
the 2
fragments (originally taken from test9.jsp in testsuite):
1. The code that works creates the variable "_toto" in the java
compiler
The code that doesn't work creates the variable "toto" in the
jsp
runtime by calling the shared lib classes which inserts it into
the page
with the following code:
(taken from org.apache.pluto.tags.BasicURLTag.doEndTag)
pageContext.setAttribute (var, url.toString(),
PageContext.PAGE_SCOPE);
2. <bodycontent>empty</bodycontent> tags work, compound ones do
not
ex: <portlet:namespace/> works, <portlet:actionURL
var="url"></portlet:actionURL> does not work
Local fix
place this jar file in their <WAS HOME>/classes directory,
restart the
server and run their testcase to see if the problem is resolved.
make sure files under WAS_HOME/Temp are deleted, so the new
class files are created as a result of recompiling of the jsp
files
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server 5.0.2.x and *
* 5.1.1.x users whose application jsp files *
* use attributes to define variables within *
* a custom tag *
****************************************************************
* PROBLEM DESCRIPTION: When attempting to output the values *
* of these variables from the jsp file, *
* the output of null is received, *
* although the variable is defined *
* through an attribute within the *
* custom tag. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This problem is reported on WAS v5.1.1, but the same problem
exists on v5.0.2.x and the current version of WAS5.1.1.x
Problem conclusion
Variable declaration for attributes within custom tags is
added in webcontainer code at the end of the custom tag
processing
The fix for this APAR is currently targeted for inclusion in
fixpack 5.02.10 and 5.1.1.4. Please refer to the Recommended
Updates page for delivery dates:
http://www-1.ibm.com/support/docview.wss?rs=180&context=SSEQTP
&uid=swg27004980
Temporary fix Comments
APAR information |
APAR number |
PQ97977 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
10W |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-12-03 |
Closed date |
2005-01-31 |
Last modified date |
2005-01-31 |
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 |
|