[
https://issues.apache.org/jira/browse/WICKET-6050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15055761#comment-15055761
]
Martin Grigorov commented on WICKET-6050:
-----------------------------------------
I think the functionality should be opt-in, i.e. only Ajax behaviors which want
to serialize everything should explicitly ask for it. This way it will be
backward compatible too.
> Wicket Ajax (Wicket.From.serializeElement) causes 400 bad request
> -----------------------------------------------------------------
>
> Key: WICKET-6050
> URL: https://issues.apache.org/jira/browse/WICKET-6050
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.21.0
> Reporter: Rakesh A
> Attachments: WICKET-5948-2.7z
>
>
> Due to the recent change (WICKET-5948) in Wicket Ajax (JavaScript), Ajax
> calls add nested form element values as request parameters and result HTTP
> status code 400 when URL gets too long.
> This happens when you add an Ajax behavior (custom event triggered from
> JavaScript) to a DOM element with nested form fields.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
