Details
Description
If I use <f:ajax disabled="true"/> on a command button then stale FacesMessages are displayed by <h:messages />.
Activity
Adrian Gygax
created issue -
Adrian Gygax
made changes -
Field | Original Value | New Value |
---|---|---|
Attachment | ice7432.war [ 13730 ] |
Adrian Gygax
made changes -
Attachment | ice7432.war [ 13731 ] |
Adrian Gygax
made changes -
Attachment | ice7432.war [ 13730 ] |
Ted Goddard
made changes -
Assignee | Ken Fyten [ ken.fyten ] |
Tyler Johnson
made changes -
Salesforce Case | [5007000000JN2YJ] |
Ken Fyten
made changes -
Fix Version/s | 2.1 [ 10241 ] | |
Assignee Priority | P2 | |
Assignee | Ken Fyten [ ken.fyten ] | Mark Collette [ mark.collette ] |
Ken Fyten
made changes -
Affects | [Compatibility/Configuration] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #27299 | Fri Jan 20 18:53:06 MST 2012 | mark.collette | |
Files Changed | ||||
MODIFY
/icefaces3/trunk/icefaces/core/src/main/java/org/icefaces/impl/event/FacesMessagesPhaseListener.java
|
Mark Collette
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
Attached a sample project to demonstrate the issue.
Steps to reproduce the problem:
1. Enter "asdf" in both text fields
2. Press the button. Notice the two correctly shown error messages.
3. Clear the second text field.
4. Press the button again. Notice that still BOTH error messages are shown, even if the second field is now valid!
Options which don't show the problem:
All of these options are not feasible workarounds in our case.
<f:ajax disabled="true"/> is needed to trigger a full page refresh in a Portal environment