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

Bug 433688

Summary: [BrowserFunction] Uncaught exceptions cause server error on the client
Product: [RT] RAP Reporter: Wolfgang Pedot <wolfgang.pedot>
Component: RWTAssignee: Project Inbox <rap-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: minor    
Priority: P2 CC: mknauer
Version: 2.3   
Target Milestone: 2.3 M3   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Wolfgang Pedot CLA 2014-04-28 13:54:29 EDT 
Uncaught exceptions in a BrowserFunction will cause a HTTP-Error 500 on the client because "renderFunctionResult" in BrowserLCA will fail with a NullPointerException. I am pretty sure that in 2.2 RuntimeExceptions (or at least their messages) were transported to the client side and did not break the client so I guess this is a newly introduced problem.

An easy fix is to set a JsonValue.NULL result if there is an exception, this will cause the error to appear as JavaScript exception on the client.
Comment 1 Ivan Furnadjiev CLA 2014-04-29 07:24:20 EDT 
Fixed in master with change https://git.eclipse.org/r/25691.