Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Remote Application Platform (RAP) » Client side error handling with RAP
Client side error handling with RAP [message #1802110] Fri, 01 February 2019 09:48 Go to next message
Linuxhippy Mising name is currently offline Linuxhippy Mising nameFriend
Messages: 36
Registered: July 2009
Member
Hi,

I wonder - can client-side error handling be done with RAP? And does RAP expose a public API for it (very much like ClientListener is available for events)?

We've several scenarios where it would be great to be able to react to error happening in the client-part of out RAP applications, e.g.:
- react/log exceptions caused by out code in ClientListeners
- handle issues with RAP itself (like the recently discovered BrowserFunction race conditions)
- react to / log connection issues, e.g. when out authetication server forces a re-login. currently RAP displayes the "server not available" popup, which is quite misleading for users.

Thank you in advance, Clemens
Re: Client side error handling with RAP [message #1802111 is a reply to message #1802110] Fri, 01 February 2019 10:35 Go to previous message
Ivan Furnadjiev is currently offline Ivan FurnadjievFriend
Messages: 2327
Registered: July 2009
Location: Sofia, Bulgaria
Senior Member
Hi Clemens,
you could patch RAP "rwt.runtime.ErrorHandler" at runtime or with external JS file (client-side mixin). There are mainly two public static functions, which names are self explained:
- processJavaScriptErrorInResponse
- processJavaScriptError

You could completely override them or just handle specific scenarios, like specific server error.

HTH,
Ivan
Previous Topic:Copy, Tabulation and Search features in RAP widgets
Next Topic:Copy to clipboard
Goto Forum:
  


Current Time: Thu Dec 12 18:27:17 GMT 2019

Powered by FUDForum. Page generated in 0.01971 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top