Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 395677

Summary: Allow to register an exception handler when running in JEE mode
Product: [RT] RAP Reporter: RĂ¼diger Herrmann <ruediger.herrmann>
Component: RWTAssignee: Project Inbox <rap-inbox>
Status: RESOLVED DUPLICATE QA Contact:
Severity: major    
Priority: P3    
Version: 2.0   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description RĂ¼diger Herrmann CLA 2012-12-04 04:37:17 EST
When running in JEE operation mode, application code has no chance to prevent runtime exceptions from being propagated to the servlet engine. Which in turn delivers an HTTP 500 error page.
There is curently no way to control how exceptions from application code are handled. Without exception handling, RWT standalone can hardly be used in real word applications.

I suggest to provide API to register an exception handler. There remain some questions though:
* where should the exception handler be registered, ApplicationConfiguration.setExceptionHandler()?
* what should be the scope of the exception handler, one per session, one per application?
* what about SWT mode, would the usual JFace exception handler interfere with the new 'outer' exception handler?
* should there be a default exception handler?
* what exceptions should be passed to the exception handler, Throwable or Exception?
Comment 1 Ralf Sternberg CLA 2012-12-05 04:20:44 EST
We already have bug 367773 for this. Will copy your comments to this bug.

*** This bug has been marked as a duplicate of bug 367773 ***