A friendly place for programming greenhorns!
Big Moose Saloon
Register / Login
Win a copy of
Elasticsearch in Action
this week in the
The response could not be deserialized
Joined: Sep 06, 2013
Sep 11, 2013 00:01:10
my earlier gwt version was 2.2.0 and gxt was 2.2.3 and now i want to upgrade it to gwt version 2.5.1 and gxt as 2.2.5
In dev mode the application works fyn but when i deploy the application and run it it shows me the following service failure error
"The response could not be deserialized "
Joined: Jul 26, 2007
Sep 11, 2013 00:13:44
Please post the full stack trace for us to help you figure out whats going wrong.
Taking a wild guess, this could be because your response POJO does not implement Serializable and/or have the default constructor
How to ask questions
Donate a pint, save a life!
Onff-turn it on!
I agree. Here's the link:
subject: The response could not be deserialized
GWT Dev mode Changes in the Java class is not reflecting when refresh the browser
GWT Designer not supported GXT API's
Unable to view the GXT-GWT chart when deployed on Tomcat Server
New GXT for GWT 2.0 Released
Working with UTF16 encoed chars in GWT/GXT
All times are in JavaRanch time: GMT-6 in summer, GMT-7 in winter
| Powered by
Copyright © 1998-2015