[
https://issues.apache.org/jira/browse/WICKET-6050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15055669#comment-15055669
]
Rakesh A commented on WICKET-6050:
----------------------------------
By adding Wicket.Form.excludeFromAjaxSerialization[markupId] = 'true'; it
probably can be avoided, but this needs to be done to all behaviors that were
written prior to v6.21.0 (consider behaviors written for UI component
integration - WiQuery, etc).
WICKET-5948 change in 6.21.0 has more impact I think.
> 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)
