The correct way is to override doUnexpectedFailure(Throwable
e)<http://google-web-toolkit.googlecode.com/svn/javadoc/2.0/com/google/gwt/user/server/rpc/AbstractRemoteServiceServlet.html#doUnexpectedFailure(java.lang.Throwable)>in
your custom RPC Servlet. That way you won't have to change GWT's code.
--Sri
On 14 January 2011 04:31, pete <superp...@geekcity.de> wrote:
> I actually found out how I can solve at least my case, I just extended
> RemoteServiceServlet (which I had done anyway with a
> GuiceRemoteServiceServlet). There in the catch clause of public String
> processCall(String payload){...} I just added my Log command, not it
> works and I see the RPC exceptions...
> Thanks anyway for the replies :-)
>
>
> On Jan 13, 10:22 am, SVR <svr...@gmail.com> wrote:
> > true, I don't see the ability to configure server side log anywhere.
> > I would try this:
> > Enable gwt.logging.firebugHandler and see atleast the umbrella
> exception...
> >
> > On Thu, Jan 13, 2011 at 6:32 AM, pete <superp...@geekcity.de> wrote:
> > > Yes, but what about RPC-exceptions, that actually don't arrive
> > > anywhere? (I think that is the case, where I'm stuck, but I have no
> > > access to the deployed production webapp, and I'm told, that the logs
> > > show nothing...)
> > > I mean, if I actually arrive in the correct function on the server,
> > > yes, then I could just do the logging as I'm used to.
> > > I just think, I changed the return-value of an existing function and
> > > somehow there is a problem somewhere, that I don't arrive in that
> > > function anymore, or that the answer doesn't arrive back. If I look at
> > > the firebug console, I see that my post-request fails, but I
> > > surrounded the whole method, which is in question with try{..}catch()
> > > {log} and still nothing... Which makes me think, I never arrive in
> > > that method, and something goes wrong earlier... Or later, I don't
> > > know...
> > > But I would need a stacktrace to be logged like "method bla doesn't
> > > support correct return type - TargetInvocationExcaption: Stacktrace"
> > > in such a case. But I don't know how to log those things.
> > > In development mode, yes, then I see any stacktrace like this. But
> > > unfortunately there it works and I need to know what goes wrong with
> > > the deployed version, and then there is no log at all (even though it
> > > says "check server log")
> > > Is there any way to configure log4j to log those exceptions?
> >
> > > On Jan 12, 11:23 pm, SVR <svr...@gmail.com> wrote:
> > > > You could catch and throw the same way you would do in any java
> appln.
> >
> > > > On Wed, Jan 12, 2011 at 5:16 PM, pete <superp...@geekcity.de> wrote:
> > > > > Hallo,
> >
> > > > > is there a way to show stacktraces of UnexpectedExceptions after
> the
> > > > > webapp is deployed? I have logging enabled in general, if I
> manually
> > > > > use my logger, like LOG.debug("blah"), I can see my logs...
> > > > > If RPC fails, I just get an unexpected exception saying "the call
> > > > > failed on the server, see server logs for details", however, there
> is
> > > > > no stacktrace or exception logging anywhere, not even in
> System.out,
> > > > > etc.
> > > > > How can I enable this? Or where does GWT save those server logs
> > > > > mentioned? Is it possible to configure log4j to log those
> exceptions?
> > > > > Help would really be appreciated, since googling hasn't really
> shown
> > > > > up anything I could use...
> >
> > > > > Regards,
> > > > > Peter
> >
> > > > > --
> > > > > 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<google-web-toolkit%2bunsubscr...@googlegroups.com>
> <google-web-toolkit%2bunsubscr...@googlegroups.com<google-web-toolkit%252bunsubscr...@googlegroups.com>
> >
> > > <google-web-toolkit%2bunsubscr...@googlegroups.com<google-web-toolkit%252bunsubscr...@googlegroups.com>
> <google-web-toolkit%252bunsubscr...@googlegroups.com<google-web-toolkit%25252bunsubscr...@googlegroups.com>
> >
> >
> > > > > .
> > > > > 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
> google-web-toolkit@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > > google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com>
> <google-web-toolkit%2bunsubscr...@googlegroups.com<google-web-toolkit%252bunsubscr...@googlegroups.com>
> >
> > > .
> > > 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 google-web-toolkit@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com>
> .
> 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 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.
