DWR

Please see:
ExceptionConverter for java.lang.Exception is not working in DWR 3

From the DWR users mailing list:

theonix wrote:
In DWR 2.0.3 I could have:
<convert converter="exception" match="...cardorder.exceptions.InvalidTopupAmountException"></convert>
<convert converter="exception" match="java.lang.Exception" javascript="AjaxException"></convert>
where the converter for java.lang.Exception is after InvalidTopupAmountException.
This doesn't work in DWR 3.0, because now the order matters. So the converter for java.lang.Exception have to be before any other exception converter.
I changed the order in my dwr.xml and it works perfectly.

mikewse wrote:
I think this quirk only appears when you are using class-mapping (the javascript attribute) as that alters the order of converter lookup somewhat.