I appreciate the help.  I'm talking about a runtime exception from
client code while in hosted mode.  These exceptions are silent for
me.  How can I at least be informed that an error occurred?

On Sep 23, 10:11 am, Venkatesh Babu <venkatbab...@gmail.com> wrote:
> If you client code has try catch blocks to catch the exceptions, then you
> can use the GWT logging framework and put the exception logging statements
> in the catch block. That'll log the exception into your server logs.
> Otherwise, I'm not sure if GWT provides the infrastructure to show exception
> stack trace on console because when the client code is running on browser as
> javascript there is no underlying console. May be the exceptions get
> translated into javascript errors.
>
> Thank you,
> Venkatesh
>
> On Wed, Sep 23, 2009 at 12:54 PM, tieTYT <tie...@gmail.com> wrote:
>
> > That doesn't sound right... what if an exception occurred on startup
> > on the client side?  There wouldn't even be an RPC Servlet involved
> > yet.
>
> > On Sep 22, 6:38 pm, Sripathi Krishnan <sripathi.krish...@gmail.com>
> > wrote:
> > > Override the doUnexpectedFailure(Throwable t)  method in your RPC
> > Servlet.
> > > This method gets called whenever an exception escapes your method. You
> > can
> > > log the stacktrace/message in this method.
>
> > > --Sri
>
> > > 2009/9/22 tieTYT <tie...@gmail.com>
>
> > > > When I'm in hosted mode, if my client code throws a runtime exception,
> > > > it seems to be swallowed and not reported.  For example, if I put a
> > > > "throw new NullPointerException()" at the end of a method.  I can use
> > > > the debugger to find the exact line that's throwing the exception but
> > > > when it occurs it just fails silently.  There's no info in the Shell
> > > > or on the console and the app doesn't even necessarily act like there
> > > > was an error.
>
> > > > I'm not very familiar with our code or GWT so I have to ask: is this
> > > > normal, expected GWT behavior or is our code failing to print a stack
> > > > trace?
>
> > > > If this is GWT's fault, what's the work around?  Someone on the irc
> > > > channel suggested I wrap all my client code around a try/catch but
> > > > that seems a little inconvenient and messy.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to