PI86494: MESSAGES RETURNED FROM JSF APIS ARE IN THE INCORRECT ORDER

Fixes are available

APAR status

Closed as program error.

Error description

When reading messages using JSF APIs:

FacesContext#getClientIdsWithMessages()

and

FacesContext#getmessages(String clientId).

Messages are supposed to be returned in the order in which they
were added.


The messages are added in the order in which the validation is
performed, which is supposed to be the DOM order of the
elements within the facelet.

However, the message order being provided by the JSF
implementation does not agree with the facelet DOM order as it
should.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server            *
*                  Traditional                                 *
*                  Profile versions 8.0, 8.5.5 and Liberty     *
*                  Profile users of JavaServer Faces (JSF)     *
*                  MyFaces 2.0                                 *
****************************************************************
* PROBLEM DESCRIPTION: The order of messages displayed when    *
*                      using h:messages does not match         *
*                      component                               *
*                      order                                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When the <h:messages/> component is used, the order of messages
might not match the component order - leading to an inconsistent
order of displayed messages.

Problem conclusion

The JSF MyFaces 2.0 code was updated to fix the order of
messages displayed in <h:messages/> component.
Fix details can be found at
https://issues.apache.org/jira/browse/MYFACES-3579

The fix for this APAR is currently targeted for inclusion in fix
pack 8.0.0.15 and 8.5.5.13 for WebSphere Application Server
Traditional Profile and 17.0.0.3 for WebSphere Application
Server Liberty Profile. 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
PI86494
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-08-28
Closed date
2017-09-14
Last modified date
2017-10-02

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
WEBS APP SERV N
Fixed component ID
5724H8800

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:
03 May 2022

Tips

PI86494: MESSAGES RETURNED FROM JSF APIS ARE IN THE INCORRECT ORDER

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?