[jira] Resolved: (WICKET-3131) Retest all combinations of redirect policies and render strategies

["Martin Grigorov (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Grigorov resolved WICKET-3131.
-------------------------------------

       Resolution: Not A Problem
    Fix Version/s: 1.5-M4

I just retested my biggest application with all render strategies and there are no issues so far.
The attached patch could be ignored because it was fixed with WICKET-3143 (No Exception page are rendered when using ajax) 

> Retest all combinations of redirect policies and render strategies
> ------------------------------------------------------------------
>
>                 Key: WICKET-3131
>                 URL: https://issues.apache.org/jira/browse/WICKET-3131
>             Project: Wicket
>          Issue Type: Sub-task
>          Components: wicket
>    Affects Versions: 1.5-M2.1
>            Reporter: Martin Grigorov
>            Assignee: Martin Grigorov
>             Fix For: 1.5-M4
>
>         Attachments: WICKET-3131.patch
>
>
> While debugging problem "ajax links example - failure handler is not invoked, instead error is reported" in WICKET-3114 I found that using redirect policy "NEVER_REDIRECT" doesn't quite work because the response body is already written when Wicket tries to write the headers (org.apache.wicket.request.handler.render.WebPageRenderer.respond(RequestCycle), around line 203).
> So failures in processing Ajax request cannot successfully return http status "500" to wicket-ajax.js.
> I think we need to retest all possible combinations of redirect policies and render strategies and add unit tests for them if possible.

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