Use the portal exception handling mechanism when Gradebook encounters uncaught exception

This issue was imported from github issues. The use of Github issues as a bug tracker was an experiment with the GradebookNG (now just called Gradebook) tool development, released with Sakai 11. The information here may not be 100% accurate, please update or comment if any of the fields need updating.

No good solution for this at this time. Closing.

I wasn't super excited about the solution above, so I had a look at the other wicket apps in Sakai. It looks like Delegated Access re-raises any exceptions which brings it to the attention of the portal error handler. Perhaps that's the right approach here?

I think the only issue with that approach is that any exceptions that occur on an AJAX request are returned as a 500s may be missed by the user (it's logged in the console but Wicket doesn't catch the exception and do anything meaningful with it). An approach might be add a global AJAX error handler to insert the exception into the page upon receiving it. Maybe something like this: https://github.com/sakaiproject/sakai/compare/master...payten:3292-exception-handling (there faux exceptions on the Settings page and Add Gradebook action)

Still not a perfect solution, but maybe getting warmer? Blergh!

Have a look in GradebookNgApplication - there is a RequestCycleListener which intercepts checked Exceptions and redirects to ErrorPage which is our own 'Something went wrong' page. It might need a bit of a rework to pass off to the portal exception handler.

If not, we could just rework ErrorPage to do a similar thing and have a collapsed stack trace maybe.