You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Eelco Hillenius (JIRA)" <ji...@apache.org> on 2007/03/09 17:49:10 UTC

[jira] Closed: (WICKET-372) Runtime Exception handling with ajax requests

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

Eelco Hillenius closed WICKET-372.
----------------------------------


> Runtime Exception handling with ajax requests
> ---------------------------------------------
>
>                 Key: WICKET-372
>                 URL: https://issues.apache.org/jira/browse/WICKET-372
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 1.2.6, 1.3, 2.0
>            Reporter: Eelco Hillenius
>             Fix For: 1.3, 2.0
>
>
> I just found out that exception handling with Ajax doesn't work properly in development mode or when a user provides a custom error page instance in a custom request cycle. The problem is that the error page is never displayed.
> This is strange, as setResponsePage with a page instance in an ajax request works fine. To illustrate this problem, I added another link to the ajax links example.
> I'm at a loss why this doesn't work currently.

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