gwt-rpc

I'm getting the following exception: com.google.gwt.user.client.rpc.SerializationException: Type 'java.lang.Long' was not included in the set of types which can be serialized by this SerializationPolicy or its Class object could not be loaded. For security purposes, this type will not be serialized using GWT 2.1 and the built in Jetty server. According to the docs, this type is definitely serializable... How can I include it in the SerializationPolicy? Krzysztof Uroda Here's the link that should resolve problem: http://developerlife.com/tutorials/?p=131 A user defined class is serializable if:

we are haunted by occasional occurences of exceptions such as: com.google.gwt.user.client.rpc.SerializationException: Type 'xxx' was not assignable to 'com.google.gwt.user.client.rpc.IsSerializable' and did not have a custom field serializer.For security purposes, this type will not be serialized.: instance = xxx at com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serialize(ServerSerializationStreamWriter.java:610) at com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamWriter.writeObject(AbstractSerializationStreamWriter.java:129) at com.google.gwt.user.server.rpc

First of all, I know that doing a synchronous call is "wrong", and know that "is not possible". But, in a situation a lot complex (i dont know how to explain), i need to wait the response from server, I'am using the GWT-Platform command implementation for the GWT RPC calls. I was looking for some kind of "hack" for doing this. Thanks in advance. There is a solution but it is not easy (e.g. you cannot flip a single parameter to make it work). GWT is using normal JS XMLHttpRequest under the hood. In GWT there is an overlay type for it called com.google.gwt.xhr.client.XMLHttpRequest. This class

I'm using the following code as part of the GWT server-side class (servlet) for GWT-RPC. private void getImage() { HttpServletResponse res = this.getThreadLocalResponse(); try { // Set content type res.setContentType("image/png"); // Set content size File file = new File("C:\\Documents and Settings\\User\\image.png"); res.setContentLength((int) file.length()); // Open the file and output streams FileInputStream in = new FileInputStream(file); OutputStream out = res.getOutputStream(); // Copy the contents of the file to the output stream byte[] buf = new byte[1024]; int count = 0; while ((count

What is the purpose of the IsSerializable interface in GWT (regarding the RPC mechanism). I have never been able to find a good explanation as to why it is the way it is and why the default Java Serializable tagging interface does not work. Both Serializable and IsSerializable work, according to the GWT serialization docs : A user-defined class is serializable if all of the following apply: It is assignable to IsSerializable or Serializable, either because it directly implements one of these interfaces or because it derives from a superclass that does All non-final, non-transient instance

I've run through the Google Web Toolkit StockWatcher Tutorial using Eclipse and the Google Plugin , and I'm attempting to make some basic changes to it so I can better understand the RPC framework. I've modified the "getStocks" method on the StockServiceImpl server-side class so that it returns an array of Stock objects instead of String objects. The application compiles perfectly, but the Google Web Toolkit is returning the following error: "No source code is available for type com.google.gwt.sample.stockwatcher.server.Stock; did you forget to inherit a required module?" It seems that the

I am trying to figure out if I should migrate my gwt-rpc calls to the new GWT2.1 RequestFactory cals. Google documentation vaguely mentions that RequestFactory is a better client-server communication method for "data-oriented services" What I can distill from the documentation is that there is a new Proxy class that simplifies the communication (you don't pass back and forth the actual entity but just the proxy, so it is lighter weight and easier to manage) Is that the whole point or am I missing something else in the big picture? The big difference between GWT RPC and RequestFactory is that