[
https://issues.apache.org/jira/browse/MYFACES-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100140#comment-13100140
]
Jakob Korherr commented on MYFACES-3300:
----------------------------------------
Hi Michi,
Here are the 2.1.2 release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600&version=12316512
Could you provide an example-war that shows the problem?
I am wondering if we should stop the 2.1.3 release, b/c of this issue. WDYT?
Regards,
Jakob
> 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
>
> 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
