PI14513: PARENT NAMING-CONTAINER NOT REFLECTED IN CLIENT-ID

Fixes are available

APAR status

Closed as program error.

Error description

Parent naming-container not reflected in  client-id
This problem occurs in an application that uses
WAS-MyFaces-Implementation with  Apache Tobago as
JSF-Component-Library when run in
Development-Mode (facelets.DEVELOPMENT=true)

WebSphere Application Server V8.5.5.0
Distributed operating systems.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server Full       *
*                  Profile versions 8.0 and 8.5.5 and Liberty  *
*                  Profile version 8.5.5 users of              *
*                  JavaServer Faces(JSF) MyFaces.              *
****************************************************************
* PROBLEM DESCRIPTION: When the javax.faces.PROJECT_STAGE is   *
*                      set to DEVELOPMENT and JavaServer       *
*                      Pages (JSPs) are used, components       *
*                      extending UIInput do not prepend        *
*                      their parent NamingContainer's ID to    *
*                      their own ID.                           *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When the Project Stage is set to Development and JSPs are
used, parent NamingContainer IDs are not reflected in their
children's IDs when those children components extend UIInput.
For example, given
<h:form id="form">
<h:inputTextarea id="text" value="PI14513"/>
</h:form>
The h:inputTextarea component will be rendered with an ID of
"text" rather than the expected ID of "form:text".

Problem conclusion

The JSF MyFaces code was updated to check if a component is in
view and has a parent. To enable this behavior, set the
following context parameter to "true":
com.ibm.ws.jsf.PREPEND_PARENT_ID_IN_DEVELOPMENT
(true/false-default).

The fix for this APAR is currently targeted for inclusion in
fix pack 8.0.0.9 and 8.5.5.3. 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
PI14513
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-03-26
Closed date
2014-05-14
Last modified date
2014-05-14

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

R800 PSY
UP
R850 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022

Tips

PI14513: PARENT NAMING-CONTAINER NOT REFLECTED IN CLIENT-ID

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

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?