PM21875: AJAX REQUEST NESTED IN THE <HX:DATAITERATOR> TAG DOES NOT RENDER PROPERLY WITH JSF 1.2

Fixes are available

APAR status

Closed as program error.

Error description

When there is a <hx:dataIterator> which does not have an id
attribute set, AJAX request fails to render properly.

Local fix

Add the ID attribute to the <hx:dataIterator> tag to prevent
duplicate IDs. For example:
<hx:dataIterator value="{value1}" var="var1" id="dataIterator1">

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server Version    *
*                  7.0 users of the Sun RI JavaServer Faces    *
*                  (JSF) implementation version 1.2.           *
****************************************************************
* PROBLEM DESCRIPTION: JSF components, which do not            *
*                      explicitly set an id attribute, can     *
*                      cause AJAX requests to fail.            *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
An AJAX request might not work if it contains JSF components
with generated ids.  This can cause problems because AJAX
stores the id from the original request
and it can possibly change between requests.  This appears to
be more prevalent in a Portal environment as the ids generated
are based on an internal PageContext counter which can be
difficult to manage in a Portal environment when AJAX requests
are used.

Problem conclusion

The recommended approach to solving this issue is to
explicitly set the id on the JSF components.  However, the JSF
implementation was modified to allow the generated IDs to
remain the same across requests.  Under rare conditions this
could possibly result in duplicate ids being generated.  To
enable this behavior, the following context parameter must be
set to "true" in the applications web.xml file :

com.ibm.ws.jsf.DISABLE_PC_APPEND_ON_ID

An example entry is:

<context-param>
<param-name>com.ibm.ws.jsf.DISABLE_PC_APPEND_ON_ID</param-name>
<param-value>true</param-value>
</context-param>

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.15.  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
PM21875
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-09-02
Closed date
2010-10-20
Last modified date
2010-10-20

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

[{"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:
24 October 2021

Tips

PM21875: AJAX REQUEST NESTED IN THE <HX:DATAITERATOR> TAG DOES NOT RENDER PROPERLY WITH JSF 1.2

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?