For the purposes of getting stack traces, SuperDevMode is the same as production mode. For this, you have two options: (1) Deobfuscate your stack traces on the server (see StackTraceDeobfuscator) (2) Emulated stack traces
When you do either or both of these, you still don't get something quite as reliable as Dev Mode for stack traces, but it's usually good enough. Paul On 12/09/12 19:45, David Sauvier wrote: > How can we see Runtime Exceptions in SuperDevMode? > > In regular Dev Mode we were able to get a nice StackTrace through all the > Java Classes. > > Currently, to get client logging back to the eclipse console I'm using remote > logging and have an uncaught exception handler with a buildstack trace > method. But it still builds an archaic javascript type report. It's not the > nice stack trace we had in regular dev mode. > > I understand about Sourcemaps on the browser and have those set-up and am > contemplating looking into setting breakpoints and the such. > > But I want to see if there is a way to get the nice Java stack traces back. > > Thanks, > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-web-toolkit/-/vrSwtPRZy28J. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
