Account Options

  1. Sign in
The old Google Groups will be going away soon.
Switch to the new Google Groups.
Google Groups Home
« Groups Home
RPC bug in 1.1.0
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  6 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Tim  
View profile  
 More options Aug 15 2006, 11:44 am
From: "Tim" <kata...@gmail.com>
Date: Tue, 15 Aug 2006 08:44:46 -0700
Local: Tues, Aug 15 2006 11:44 am
Subject: RPC bug in 1.1.0
Sending data from the server -> client works fine.
Sending data from the client -> server doesn't.

The issue is an index out of bounds (stack trace below). Editing the
jar, I've found that it tries to access up to an index of 26, despite
the size being only 9.

[WARN] StandardContext[]Exception while dispatching incoming RPC call
java.lang.IndexOutOfBoundsException: Index: 9, Size: 9
        at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.extract (ServerSerializationStreamReader.java:259)
        at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.deseria lizeStringTable(ServerSerializationStreamReader.java:207)
        at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.prepare ToRead(ServerSerializationStreamReader.java:80)
        at
com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServi ceServlet.java:181)
        at
com.google.gwt.user.server.rpc.RemoteServiceServlet.doPost(RemoteServiceSer vlet.java:147)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
        at
com.google.gwt.dev.shell.GWTShellServlet.service(GWTShellServlet.java:175)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
        at
org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:239)


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Scott Blum  
View profile  
 More options Aug 15 2006, 12:03 pm
From: "Scott Blum" <sco...@google.com>
Date: Tue, 15 Aug 2006 09:03:41 -0700
Local: Tues, Aug 15 2006 12:03 pm
Subject: Re: RPC bug in 1.1.0
Tim,

There is a known issue with client->server serialization when the same
object is serialized multiple times.  There's a workaround here that
should hopefully fix the problem.

http://groups.google.com/group/Google-Web-Toolkit/browse_thread/threa...

Scott


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Tim  
View profile  
 More options Aug 15 2006, 12:25 pm
From: "Tim" <kata...@gmail.com>
Date: Tue, 15 Aug 2006 09:25:12 -0700
Local: Tues, Aug 15 2006 12:25 pm
Subject: Re: RPC bug in 1.1.0
I tried this, didn't fix the issue.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Tim  
View profile  
 More options Aug 15 2006, 1:52 pm
From: "Tim" <kata...@gmail.com>
Date: Tue, 15 Aug 2006 10:52:34 -0700
Local: Tues, Aug 15 2006 1:52 pm
Subject: Re: RPC bug in 1.1.0
The data sent from the server to the client is completetly different
than what the client is sending back to the server, is this intended?

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Scott Blum  
View profile  
 More options Aug 15 2006, 2:01 pm
From: "Scott Blum" <sco...@google.com>
Date: Tue, 15 Aug 2006 11:01:24 -0700
Local: Tues, Aug 15 2006 2:01 pm
Subject: Re: RPC bug in 1.1.0
Yes, the client->server and server->client formats are slightly
different to optimize performance.  It's the same basic structure, just
organized and delimited differently.

If that didn't fix the issue (and you've recompiled/cleared browser's
cache/etc), then I'm not sure what to tell you without looking at your
project.

Scott


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Tim  
View profile  
 More options Aug 15 2006, 2:09 pm
From: "Tim" <kata...@gmail.com>
Date: Tue, 15 Aug 2006 11:09:12 -0700
Local: Tues, Aug 15 2006 2:09 pm
Subject: Re: RPC bug in 1.1.0
I've figured out the problem.

My data structures were in this logic.

Master data class contained sub data classes
sub data classes contained char[] array.

if the char[] array contained a value of 0 anywhere inside it, the
token system on the server would stop at that point as a string
terminator. It looks like gwt needs to do something about char array's
containing 0.

For now I'll just explicitly set all 0's to 1 before sending.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »