I'm slowly moving to using more and more JsInterop instead of JSNI in our application (I know, I'm late).
The app has a so far reliable uncaught exception handler (GWT.setUncaughtExceptionHandler) and we use $entry for callbacks from JSNI.
But when getting an exception in a JsInterop callback, the exception and stack trace are now totally unusable (in SuperDevMode):
Throwable.java:120 Uncaught Error: java.lang.RuntimeException
at RuntimeException_1_g$.createError_0_g$ [as createError_2_g$] (Throwable.java:120)
at RuntimeException_1_g$.initializeBackingError_0_g$ [as initializeBackingError_1_g$] (Throwable.java:112)
at RuntimeException_1_g$.Throwable_1_g$ (Throwable.java:60)
at RuntimeException_1_g$.Exception_1_g$ (Exception.java:25)
at new RuntimeException_1_g$ (RuntimeException.java:25)
at Function.onSuccess_383_g$ (BrowserFileSystemPlatform.java:78)
at lambda_0_g$ (Runtime.java:166)
Obviously there is no $entry around the callbacks.How can I fix this and get usable stack traces again?
Thanks,
Thomas
-- You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/400e1d88-1118-4b3b-bfae-d1785c262f8dn%40googlegroups.com.
No comments:
Post a Comment