Ended up with something like this:
https://gist.github.com/xfyre/12612d45bccf16422050
Kind of a brutal approach, but works OK
On Sun, Jan 25, 2015 at 2:26 PM, Ilya Obshadko
wrote:
> I have looked into source and seems like we can't do much. AJAX exception
> reporting is hard-coded in exception-
I have looked into source and seems like we can't do much. AJAX exception
reporting is hard-coded in exception-frame.coffee and this part cannot be
properly altered.
If we don't supply X-Tapestry-ErrorMessage header, this iframe-based
exception reporting is turned off (which is good).
ajax.coffee
in 5.4 there is a custom exception handler available by contributing your
handler.
search nabble , I had similar queries 4 or 5 months ago. that should get
you started.
in 5.3, you can use the tapestry-exceptionpage package from tynamo I
believe for same behaviour.
sry for vagueness, haven't to
I asked about this before, but didn't get any answer. Is that possible to
customize AJAX error reporting in any way?
I need to have a different logic there (for example, if error occurs during
zone update, I want to remove custom zone overlay and present a modal
dialog with human-readable descript