Todd,
Yes - here's a sinppet of what happens in processCall prior to the
invocation of RPC.decodeRequest:
public String processCall(String payload) throws
SerializationException
{
try
{
long starttime = System.currentTimeMillis();
String returnvalue = "";
Response response = new Response();
RPCRequest rpcRequest = RPC.decodeRequest(payload,
this.getClass(), this);
// snip
The issue is that the one or two remote services and specific methods
that failed with this exception are commonly used throughout the
application, so, unfortunately, it is not a consistent failure of
those methods.
Also, looking at where the exception is thrown by the RPC class,
payload is an empty String, rather than a null pointer:
(RPC.java line:225-227)
if (encodedRequest.length() == 0) {
throw new IllegalArgumentException("encodedRequest cannot be
empty");
}
Which means, looking back up through the invocation history, that
RPCServletUtils.readContentAsUtf8 may be returning an empty String.
Jason
On Jan 14, 8:57 am, "[email protected]" <[email protected]>
wrote:
> So you are overriding processCall in you
> com.xxx.yyy.server.services.ZzzServerServlet class. Are you doing any
> manipulation to the payload that might make it null?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
