Clientside validation errors when using PPR
-------------------------------------------
Key: TRINIDAD-880
URL: https://issues.apache.org/jira/browse/TRINIDAD-880
Project: MyFaces Trinidad
Issue Type: Bug
Affects Versions: 1.2.4-core, 1.2.3-core
Environment: Windows XP Pro SP2, Facelets 1.1.13, Sun Java System
Application Server 9.1, JSF1.2_07-b03
Reporter: Graeme Steyn
To reproduce the problem deploy the attached sample application and execute the
following sequence of actions.
1. All radio buttons should be blank when form is first displayed - press
"Submit" - validation error occurs for first question (expected).
2. Select "Yes" for "Is English your first language?" - press "Submit" -
validation error is cleared and form re-displayed.
3. Select "No" for "Is English your first language?" - press "Submit" -
validation error occurs for second question (expected).
4. Select "Yes" for "Is English your first language?" - ppr results in second
question being disabled, not required and clears validation message.
5. Press "Submit" - validation error occurs for second question (fault).
6. Select "No" for "Is English your first language?"
7. Select "Yes" for second question. Notice that a new required field appears.
8. Press "Submit" - validation error occurs for the new field (expected).
8. Select "No" for second question. The additional required field disappears.
9. Press "Submit" - Error appears: "Field Error [certDetails] - Enter a value"
(fault).
10. Acknowledge and select "Yes" for "Is English your first language?" - press
"Submit" - 2 validation error messages occur (fault).
Using Firebug, it appears that the ppr is taking place correctly, but checking
the DOM for _english_Validators shows that all three validators are eventually
listed.
I am assuming that this is what is causing the problem, as when the lower two
fields are disabled/hidden, the validators are not removed from
_english_Validators.
It appears that the problem may be related to "TRINIDAD-96 - Validators should
be added incrementally, not set as a whole". The problem is not present in
Trinidad 1.2.2,
but does appear in 1.2.3 and 1.2.4.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
