You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Jakob Korherr (JIRA)" <de...@myfaces.apache.org> on 2011/09/08 11:59:09 UTC
[jira] [Resolved] (MYFACES-3300) Ajax behavior change from 2.1.1 to
2.1.2
[ https://issues.apache.org/jira/browse/MYFACES-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jakob Korherr resolved MYFACES-3300.
------------------------------------
Resolution: Fixed
Fix Version/s: 2.1.4-SNAPSHOT
2.0.10-SNAPSHOT
fix committed on MYFACES-3301
> Ajax behavior change from 2.1.1 to 2.1.2
> ----------------------------------------
>
> Key: MYFACES-3300
> URL: https://issues.apache.org/jira/browse/MYFACES-3300
> Project: MyFaces Core
> Issue Type: Bug
> Affects Versions: 2.1.2
> Reporter: Michael Kurz
> Assignee: Jakob Korherr
> Fix For: 2.0.10-SNAPSHOT, 2.1.4-SNAPSHOT
>
> Attachments: MYFACES-3300-test.zip
>
>
> I am currently trying to update some examples to Myfaces 2.1.2 and ran into some ajax related problems. I have a h:selectBooleanCheckbox component that collapses and expands two input fields via f:ajax. There is a value change listener for the checkbox that sets the value internally and calls renderResponse(). In f:ajax, those input fields are also listed in execute to preserve the input the user has potentially made. So far, I had no problems with this solution. The validation for the input fields did not kick in (or did not bother me) and the values were preserved.
> With 2.1.2 I have two issues:
> 1) Even if the input values are valid the values in the input fields vanish when they are expanded and collapsed again.
> 2) Now validation kicks in for invalid values and I get an error message in the browser
> This works with all older versions I tried (2.0.4, 2.1.0 and 2.1.1).
> Would be interesting to know what really changed here!
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira