[jira] Commented: (WICKET-3141) On multipart form, sendRedirect() with PageParameters are not working

[Hudson (JIRA)]

    [ 
https://issues.apache.org/jira/browse/WICKET-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926743#action_12926743
 ] 

Hudson commented on WICKET-3141:
--------------------------------

Integrated in Apache Wicket 1.5.x #473 (See 
[https://hudson.apache.org/hudson/job/Apache%20Wicket%201.5.x/473/])
    WICKET-3141 On multipart form, sendRedirect() with PageParameters are not 
working

Wrap the 'redirect to' URL in the Ajax response in CDATA to be able to handle 
properly unencoded XML


> On multipart form, sendRedirect() with PageParameters are not working
> ---------------------------------------------------------------------
>
>                 Key: WICKET-3141
>                 URL: https://issues.apache.org/jira/browse/WICKET-3141
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.4.12
>            Reporter: Fulop Levente
>            Assignee: Martin Grigorov
>             Fix For: 1.4.14, 1.5-M4
>
>         Attachments: sample.zip
>
>
> On a multipart form, calling setResponsePage(Class, PageParameters) will not 
> redirect to the requested page. 
> In the wicket ajax debug the following error appears:
> INFO: focus set on save3
> INFO: Invoking pre-call handler(s)...
> ERROR: Wicket.Ajax.Call.failure: Error while parsing response: Could not find 
> root <ajax-response> element
> INFO: Invoking post-call handler(s)...
> INFO: Invoking failure handler(s)...
> and in Firefox Error Console the following error appears:
> Error: not well-formed
> Source File: 
> http://localhost:8080/sample/?wicket:interface=:0:form:save::IActivePageBehaviorListener:0:1&wicket:ignoreIfNotActive=true&wicket:ajax=true
> Line: 1, Column: 87
> Source Code:
> <ajax-response><redirect>../?wicket:bookmarkablePage=:problem.sample.SecondPage&param1=value1&param2=value2</redirect></ajax-response>
> The problem is, that the URL from the response XML are not xml encoded.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.