Philippe, Kelsey - thanks for the very helpful responses. This sort
of additional proxy behavior feels like something that would be of
considerable value as a standard part of GWT. I'm surprised there
aren't considerably more complaints in this group.
setServiceEntryPoint() was the magic button
Jeff,
You could create a common subclass (let's call it JeffRemoteServiceServlet)
of RemoteServiceServlet that overrides the
onAfterRequestDeserialized(RPCRequest) method. That method is called, as the
name implies, everytime the servlet receives an RPC request, so it's the
perfect spot to col
The command pattern included in GWT-Platform gives a different path to each
command and yield very readable logs in GAE.
The trick is to call "setServiceEntryPoint" from the client async service
implementation. If you want to see how we do it in GWTP check out:
http://code.google.com/p/gwt-pl
Browsing through the GWT code some more, it doesn't look promising.
Is there any way to look at the output of the RpcProxyCreator?
Reading code is ok, reading code that generates code tortures my
brainmeats.
Jeff
On Tue, Mar 29, 2011 at 2:28 PM, Jeff Schnitzer wrote:
> GWT's RPC system produces
GWT's RPC system produces distinctly unfriendly access logs. When I
look at my logs (especially the GAE dashboard), every RPC basically
boils down to a single line item for the whole servlet (and all the
various RPC methods):
/mymodule/myservletNNN requests avg MMM ms each
I really want this
