[
https://issues.apache.org/jira/browse/WICKET-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087607#comment-14087607
]
Sven Meier commented on WICKET-5658:
------------------------------------
Hi Martin,
I'm worried that this change might applications on 6.x, their components will
keep the raw input and might render the wrong output afterwards.
After all these years the reporter is the first to complain about this, he
could easily use his own version of AFCUB. For Wicket 7.x we need something
added to the migration guide.
> AjaxFormComponentUpdatingBehavior should not clear the rawInput when
> updateModel is false
> -----------------------------------------------------------------------------------------
>
> Key: WICKET-5658
> URL: https://issues.apache.org/jira/browse/WICKET-5658
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.16.0
> Reporter: Ilia Naryzhny
> Assignee: Martin Grigorov
> Labels: ajax, dropdown
> Fix For: 7.0.0-M3, 6.17.0
>
>
> Setup: case requires OnChangeAjaxBehavior with getUpdateModel returning false
> on DropDownChoice.
> Result: ajax response contain model's object, but not new value.
> Explanation: There is following lines in AjaxFormComponentUpdatingBehaviour
> formComponent.inputChanged();
> formComponent.validate();
> if (formComponent.isValid())
> {
> >>>>>>>> formComponent.valid();
> if (getUpdateModel())
> {
> formComponent.updateModel();
> }
> onUpdate(target);
> }
> Let me note that "formComponent.valid()" is cleaning raw Input. But it's
> required in subsequent AbstractChoice.onComponentTagBody.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
