That article was the third result in a Google search for "gwt web mode exceptions": http://www.summa-tech.com/blog/2012/06/11/7-tips-for-exception-handling-in-gwt/ I agree that http://www.gwtproject.org/doc/latest/DevGuideLogging.html#Remote_Logging needs to be expanded.
On Thursday, July 18, 2013 3:38:15 PM UTC+2, RyanZA wrote: > > Hi Thomas, > > It would be great if you (or anybody who understands how to set it up) > could add a small article on gwtproject.org about setting up the > different methods of getting stack traces in production on exceptions? > > Thanks! > Ryan > > > > On Thu, Jul 18, 2013 at 3:30 PM, Thomas Broyer <t.br...@gmail.com<javascript:> > > wrote: > >> >> >> On Thursday, July 18, 2013 3:21:59 PM UTC+2, RyanZA wrote: >>> >>> Jens, even with source maps in Chrome, I've been unable to get stack >>> traces to work. They still print out poorly in production when an exception >>> is hit - the exceptions ignore the source maps entirely. I asked previously >>> if there is a way around it, but apparently it's a known issue - so I don't >>> think SourceMaps solve this problem yet. >>> >>> That said, the size and speed overhead here is terrible and most people >>> would avoid something that adds that much overhead in production (although >>> it would be great in development). >>> >>> What GWT needs here is something closer to what you get with proguard - >>> a mapping file created during compilation that could be used to run the >>> obfuscated/javascript exception through a utility to give the correct stack >>> trace with zero overheads. >>> I'm not entirely sure on how proguard accomplishes it, but I'd say it >>> would be the perfect solution. >>> >> >> This is what the StackTraceDeobfuscator does already. It's currently >> based on symbolMaps (GWT-specific) rather than source maps though. >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Google Web Toolkit" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/google-web-toolkit/1qDVlPGryKo/unsubscribe >> . >> To unsubscribe from this group and all its topics, send an email to >> google-web-toolkit+unsubscr...@googlegroups.com <javascript:>. >> To post to this group, send email to >> google-we...@googlegroups.com<javascript:> >> . >> Visit this group at http://groups.google.com/group/google-web-toolkit. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
