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 <ilya.obsha...@gmail.com> wrote: > 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 source shows that there is a 'failure' parameter which might > contain a callback to call upon request failure. > > However, zone.coffee doesn't let us to supply this callback in any way > (unless all its event handling is fully overridden using custom event > handlers). > > Are there any better ideas? > > > > > On Mon, Jan 5, 2015 at 9:54 AM, Chris Mylonas <ch...@opencsta.org> wrote: > >> 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 touched t5 for a cpl months and am on a boat >> taking a break from doing work at the top of the mast (bit light headed) >> >> chris >> On 05/01/2015 5:57 am, "Ilya Obshadko" <ilya.obsha...@gmail.com> wrote: >> >> > 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 description of the error in production mode). >> > >> > Any suggestions are welcome. >> > >> > -- >> > Ilya Obshadko >> > >> > > > > -- > Ilya Obshadko > > -- Ilya Obshadko
