Re: GWT 2.3.0 Deserialization issue with HashMap

2011-07-03 Thread Nicky Jha
Hi all

Please ignore below mail. I got this resolved. I had this issue because
gwt-servlet jar was incorrect in classpath(it was in two different location)

Thanks
Nicky




On Mon, Jul 4, 2011 at 8:20 AM, Nicky Jha  wrote:

>   Hi all
>
> I am facing below issue after moving to GWT 2.3.0
>
> *
>
> com.google.gwt.user.client.rpc.IncompatibleRemoteServiceException
> *: The response could not be deserialized
>
> at
> com.google.gwt.user.client.rpc.impl.RequestCallbackAdapter.onResponseReceived(
> *RequestCallbackAdapter.java:221*)
>
> at com.google.gwt.http.client.Request.fireOnResponseReceived(
> *Request.java:287*)
>
> at com.google.gwt.http.client.RequestBuilder$1.onReadyStateChange(
> *RequestBuilder.java:395*)
>
> at sun.reflect.GeneratedMethodAccessor31.invoke(Unknown Source)
>
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> *DelegatingMethodAccessorImpl.java:25*)
>
> at java.lang.reflect.Method.invoke(
> *Method.java:597*)
>
> at com.google.gwt.dev.shell.MethodAdaptor.invoke(
> *MethodAdaptor.java:103*)
>
> at com.google.gwt.dev.shell.MethodDispatch.invoke(
> *MethodDispatch.java:71*)
>
> at com.google.gwt.dev.shell.OophmSessionHandler.invoke(
> *OophmSessionHandler.java:167*)
>
> at
> com.google.gwt.dev.shell.BrowserChannelServer.reactToMessagesWhileWaitingForReturn(
> *BrowserChannelServer.java:326*)
>
> at com.google.gwt.dev.shell.BrowserChannelServer.invokeJavascript(
> *BrowserChannelServer.java:207*)
>
> at com.google.gwt.dev.shell.ModuleSpaceOOPHM.doInvoke(
> *ModuleSpaceOOPHM.java:132*)
>
> at com.google.gwt.dev.shell.ModuleSpace.invokeNative(
> *ModuleSpace.java:561*)
>
> at com.google.gwt.dev.shell.ModuleSpace.invokeNativeObject(
> *ModuleSpace.java:269*)
>
> at com.google.gwt.dev.shell.JavaScriptHost.invokeNativeObject(
> *JavaScriptHost.java:91*)
>
> at com.google.gwt.core.client.impl.Impl.apply(Impl.java)
>
> at com.google.gwt.core.client.impl.Impl.entry0(
> *Impl.java:214*)
>
> at sun.reflect.GeneratedMethodAccessor28.invoke(Unknown Source)
>
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> *DelegatingMethodAccessorImpl.java:25*)
>
> at java.lang.reflect.Method.invoke(
> *Method.java:597*)
>
> at com.google.gwt.dev.shell.MethodAdaptor.invoke(
> *MethodAdaptor.java:103*)
>
> at com.google.gwt.dev.shell.MethodDispatch.invoke(
> *MethodDispatch.java:71*)
>
> at com.google.gwt.dev.shell.OophmSessionHandler.invoke(
> *OophmSessionHandler.java:167*)
>
> at com.google.gwt.dev.shell.BrowserChannelServer.reactToMessages(
> *BrowserChannelServer.java:281*)
>
> at com.google.gwt.dev.shell.BrowserChannelServer.processConnection(
> *BrowserChannelServer.java:531*)
>
> at com.google.gwt.dev.shell.BrowserChannelServer.run(
> *BrowserChannelServer.java:352*)
>
> at java.lang.Thread.run(
> *Thread.java:619*)
>
> *Caused by: *
> *com.google.gwt.user.client.rpc.SerializationException**:
> java.util.HashMap/962170901*
>
> at com.google.gwt.user.client.rpc.impl.SerializerBase.getTypeHandler(
> *SerializerBase.java:153*)
>
> at com.google.gwt.user.client.rpc.impl.SerializerBase.instantiate(
> *SerializerBase.java:114*)
>
> at
> com.google.gwt.user.client.rpc.impl.ClientSerializationStreamReader.deserialize(
> *ClientSerializationStreamReader.java:111*)
>
> at
> com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamReader.readObject(
> *AbstractSerializationStreamReader.java:119*)
>
> at
> com.google.gwt.user.client.rpc.impl.RequestCallbackAdapter$ResponseReader$8.read(
> *RequestCallbackAdapter.java:106*)
>
> at
> com.google.gwt.user.client.rpc.impl.RequestCallbackAdapter.onResponseReceived(
> *RequestCallbackAdapter.java:214*)
>
> ... 26 more
>
>
>
>
>
> Seems its having issue in deserializing HashMap in GWT 2.3.0.
>
> It was working fine in GWT 2.2.0.
>
> Can anyone help please.
>
> Thanks in advance
>
> Nicky
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.



GWT 2.3.0 Deserialization issue with HashMap

2011-07-03 Thread Nicky Jha
 Hi all

I am facing below issue after moving to GWT 2.3.0

*

com.google.gwt.user.client.rpc.IncompatibleRemoteServiceException
*: The response could not be deserialized

at
com.google.gwt.user.client.rpc.impl.RequestCallbackAdapter.onResponseReceived(
*RequestCallbackAdapter.java:221*)

at com.google.gwt.http.client.Request.fireOnResponseReceived(
*Request.java:287*)

at com.google.gwt.http.client.RequestBuilder$1.onReadyStateChange(
*RequestBuilder.java:395*)

at sun.reflect.GeneratedMethodAccessor31.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(
*DelegatingMethodAccessorImpl.java:25*)

at java.lang.reflect.Method.invoke(
*Method.java:597*)

at com.google.gwt.dev.shell.MethodAdaptor.invoke(
*MethodAdaptor.java:103*)

at com.google.gwt.dev.shell.MethodDispatch.invoke(
*MethodDispatch.java:71*)

at com.google.gwt.dev.shell.OophmSessionHandler.invoke(
*OophmSessionHandler.java:167*)

at
com.google.gwt.dev.shell.BrowserChannelServer.reactToMessagesWhileWaitingForReturn(
*BrowserChannelServer.java:326*)

at com.google.gwt.dev.shell.BrowserChannelServer.invokeJavascript(
*BrowserChannelServer.java:207*)

at com.google.gwt.dev.shell.ModuleSpaceOOPHM.doInvoke(
*ModuleSpaceOOPHM.java:132*)

at com.google.gwt.dev.shell.ModuleSpace.invokeNative(
*ModuleSpace.java:561*)

at com.google.gwt.dev.shell.ModuleSpace.invokeNativeObject(
*ModuleSpace.java:269*)

at com.google.gwt.dev.shell.JavaScriptHost.invokeNativeObject(
*JavaScriptHost.java:91*)

at com.google.gwt.core.client.impl.Impl.apply(Impl.java)

at com.google.gwt.core.client.impl.Impl.entry0(
*Impl.java:214*)

at sun.reflect.GeneratedMethodAccessor28.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(
*DelegatingMethodAccessorImpl.java:25*)

at java.lang.reflect.Method.invoke(
*Method.java:597*)

at com.google.gwt.dev.shell.MethodAdaptor.invoke(
*MethodAdaptor.java:103*)

at com.google.gwt.dev.shell.MethodDispatch.invoke(
*MethodDispatch.java:71*)

at com.google.gwt.dev.shell.OophmSessionHandler.invoke(
*OophmSessionHandler.java:167*)

at com.google.gwt.dev.shell.BrowserChannelServer.reactToMessages(
*BrowserChannelServer.java:281*)

at com.google.gwt.dev.shell.BrowserChannelServer.processConnection(
*BrowserChannelServer.java:531*)

at com.google.gwt.dev.shell.BrowserChannelServer.run(
*BrowserChannelServer.java:352*)

at java.lang.Thread.run(
*Thread.java:619*)

*Caused by: *
*com.google.gwt.user.client.rpc.SerializationException**:
java.util.HashMap/962170901*

at com.google.gwt.user.client.rpc.impl.SerializerBase.getTypeHandler(
*SerializerBase.java:153*)

at com.google.gwt.user.client.rpc.impl.SerializerBase.instantiate(
*SerializerBase.java:114*)

at
com.google.gwt.user.client.rpc.impl.ClientSerializationStreamReader.deserialize(
*ClientSerializationStreamReader.java:111*)

at
com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamReader.readObject(
*AbstractSerializationStreamReader.java:119*)

at
com.google.gwt.user.client.rpc.impl.RequestCallbackAdapter$ResponseReader$8.read(
*RequestCallbackAdapter.java:106*)

at
com.google.gwt.user.client.rpc.impl.RequestCallbackAdapter.onResponseReceived(
*RequestCallbackAdapter.java:214*)

... 26 more





Seems its having issue in deserializing HashMap in GWT 2.3.0.

It was working fine in GWT 2.2.0.

Can anyone help please.

Thanks in advance

Nicky

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.



Re: Regarding google visualization(Annotated Timeline)

2010-07-16 Thread Nicky
The error says it all. set m_vpMainPanel width and height explicitly.
>
> com.google.gwt.core.client.JavaScriptException: (Error): Container width is
> zero. Expecting a valid width.
>  fileName:http://www.google.com/uds/api/visualization/1.0/e9f5bea2f5fcf88c5d872...
>  lineNumber: 604
>  stack: Error("Container width is zero. Expecting a valid width.")@:0

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.



Re: Login security question

2008-12-29 Thread Nicky

If you do 1) you open yourself to XSRF attacks. Read this article
(http://groups.google.com/group/Google-Web-Toolkit/web/security-for-
gwt-applications) on how to avoid this by submitting a duplicate field
with the cookie value and verifying it on the server end before
executing the request
For 2) the cookie is how tomcat figures out session to user
relationship in the first place. I believe the cookie name is
jsessionid for coorelating requests.

On Dec 29, 6:10 am, akutz  wrote:
> Per the Login Security FAQ (http://code.google.com/p/google-web-
> toolkit-incubator/wiki/LoginSecurityFAQ) I have a few questions:
>
> 1) We're storing the SID in a client-side cookie and then the GWT app
> is grabbing that and sending it to the server with each RPC request.
> How is that any different than getting the SID from the cookie on the
> server side? Theoretically if an attacker can replace the cookie, then
> wouldn't the GWT portion of the code that reads the cookie to send it
> along with the RPC request pick up the replaced cookie anyway?
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---



Re: Passing arguments into my GWT Application

2008-09-17 Thread Nicky

Search the group... 
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/85267b4604f7e70f#

On Sep 16, 3:50 pm, Joe Larson <[EMAIL PROTECTED]> wrote:
> Our main application is a WebObjects app.  We're now adding Web 2.0
> into the equation.  We're rebuilding isolated pages at first.
>
> I'm trying to figure out how to pass in from the WO app initial data
> to the GWT app.  I'd like to feed it two pieces of data:
>
> -WOInstanceID
> -A generated session ID (not the WOSessionID, but my own)
>
> I need these fields so I can initiate a proper Services connection
> back to the WO app for doing all my database work.
>
> I've tried passing arguments on the command line, but that has been
> problematic.  I can't figure out how to parse them.  The two methods
> in class GWT that return URLs seem to strip off everything after
> the ?.  Furthermore when operating in development mode (where my WO
> app is also acting as the web browser), WO gets cranky if you have a ?
> and doesn't actually load my GWT app but instead goes to my app's
> login page.
>
> Any suggestions?
>
> I thought maybe I could create some JavaScript variables from the WO
> app before including the GWT page, but I'm not quite sure how to do
> that nor if that's the best method.
>
> -Joe
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
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
-~--~~~~--~~--~--~---