I don't think it is a good idea to depend on UmbrellaException from Core. The simple alternative is to use a custom UncaughtExceptionHandler to un-stack UmbrellaException and send as separate log entries.
On Fri, Jul 11, 2014 at 6:16 AM, Jens <[email protected]> wrote: > Hi, > > In an app we have an UncaughtExceptionHandler that sends exceptions to the > backend. On the backend they will be deobfuscated, logged and used to > create automatic bug entries in an issue tracker. This works great as long > as we don't get an UmbrellaException from GWT. In that case only the first > cause will be serialized which means potential information loss. > > What do you think about special casing UmbrellaException in > SerializableThrowable, JsonLogRecord[client|server]Util and > StackTraceDeobfuscator so that additional causes don't get lost? Is it just > an oversight that its not already special cased or did you had a good > reason to decide against it? > > > -- J. > > -- > You received this message because you are subscribed to the Google Groups > "GWT Contributors" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/google-web-toolkit-contributors/0cb0b042-3063-4e8a-82ac-e784958b4857%40googlegroups.com > <https://groups.google.com/d/msgid/google-web-toolkit-contributors/0cb0b042-3063-4e8a-82ac-e784958b4857%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA3OHA1%2BU6kZ6c%2BFu%2BPsuiHUFKP0btkJvNf4eb9mFnO%3D_g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
