gwt-rpc

I have Spring MVC application where security is handled by Spring Security. UI is built using GWT which gets the data from server using RPC approach. I need to handle on UI the situation when session is expired: For example RPC AsyncCallback can get SessionExpiredException type of exception and popup the window with message like "You session is expired, please click the refresh link" or something. Did someone deal with such problem? Thanks. I suppose that for processing of incoming GWT call you use some Spring MVC controller or some servlet. It can have following logic try{ // decode payload

My problem is the infamous "StatusCodeException: 0" problem happening when using GWT 2.6.1 when accessing page via subdomain https://sub.site.com/ . Now, this happens quite sporadically for one customer using IE11 and I can't reproduce this from several distinct computers using IE11, IE10, IE9 or IE8 (not to talk about Chrome or Firefox). Accessing exactly the same webapp from https://site.com/ seems to work fine for that customer. This obviously lead me to conclusion that I'm having problem with Same Origin Policy . What is strange though is that my webapp is designed in the way that no cross

I sometimes/often get this Exception in GWT but don't know why: SEVERE: com.google.gwt.user.client.rpc.StatusCodeException: 0 java.lang.RuntimeException: com.google.gwt.user.client.rpc.StatusCodeException: 0 at Unknown.java_lang_RuntimeException_RuntimeException__Ljava_lang_Throwable_2V(Unknown Source) at Unknown.de_ctech24_simplynews_web_client_util_SimpleCallback_$onFailure__Lde_ctech24_simplynews_web_client_util_SimpleCallback_2Ljava_lang_Throwable_2V(Unknown Source) at Unknown.com_google_gwt_user_client_rpc_impl_RequestCallbackAdapter_$onResponseReceived__Lcom_google_gwt_user_client_rpc

How is GWT (Google Web Toolkit)'s RPC (Remote Procedure Call)'s for Asynchronous operations from browser/javascript to server is DIFFERENT or SIMILAR when compared to the AJAX calls ? If they are different, could someone help me understand how they are different ? I also heard that this RPC implementation does not works with all Server containers. For example, the GWT project did not work in Apache Tomcat. Moreover, is this RPC a an custom implementation of Google , or is it a standard implementation ? 1) GWT RPC uses AJAX to allow Data transfer for GWT applications. 2) GWT RPC abstracts out

UPDATE : GWT 2.3 introduces a better mechanism to fight XSRF attacks. See http://code.google.com/webtoolkit/doc/latest/DevGuideSecurityRpcXsrf.html GWT's RPC mechanism does the following things on every HTTP Request - Sets two custom request headers - X-GWT-Permutation and X-GWT-Module-Base Sets the content-type as text/x-gwt-rpc; charset=utf-8 The HTTP request is always a POST, and on server side GET methods throw an exception (method not supported). Also, if these headers are not set or have the wrong value, the server fails processing with an exception "possibly CSRF?" or something to that

I have an RPC service in GWT that needs to return a List. The List can be filled with various types of objects, all of which are serializable and all of are referenced elsewhere in my service so they should be available to GWT RPC. However, unless I put on a generic type parameter (e.g. ArrayList<String> ), GWT gives me the warning: Return type: java.util.ArrayList java.util.ArrayList Verifying instantiability java.util.ArrayList [WARN] Checking all subtypes of Object which qualify for serialization` Adding '465' new generated units Essentially, I just want a way to declare List or ArrayList