Hard to tell without seeing code or stack trace. Please provide:
1. A bit of code illustrating the main players. DTO, Service,
ServiceAsync, ServiceImpl method.
2. Stack Trace for the failure.
Regards,
Alfredo
On Wed, Apr 25, 2012 at 6:20 AM, Nitheesh Chandran
nithe...@aviamatica.com wrote:
Hi olivier,
Thanks a lot for prompt reply, The solution you said works fine if we
extend our class from RemoteServiceServlet . However in my case I am
not extending the class from RemoteServiceServlet . I am making the
use of HandlerAdapter class of spring for integrating spring wid GWT.
Is
Hi olivier,
Thanks a lot for prompt reply, The solution you said works fine if we
extend our class from RemoteServiceServlet . However in my case I am
not extending the class from RemoteServiceServlet . I am making the
use of HandlerAdapter class of spring for integrating spring wid GWT.
Is
Hi sam,
I had the same issue while integrating with acegi, what I choose was to
extract the code of RemoteServiceServlet in a helper
On Fri, Oct 17, 2008 at 8:40 AM, Sam [EMAIL PROTECTED] wrote:
Hi olivier,
Thanks a lot for prompt reply, The solution you said works fine if we
extend
Can you please share that code to me ? That will be a great help !!
--~--~-~--~~~---~--~~
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
Hi
You should call : RPC.decodeRequest(payload,this.remoteServiceClass,
*this*);
*this* being the remote servlet (SerializationPoliciyProvider)
To resolve the serialization policy (That allow the GWT serialization of
Serializable).
If no SerializationPoliciyProvider or his the resolution fails
Sorry for my poor expression...
If no SerializationPoliciyProvider is given (your case) or if the resolution
fails GWT DefaultPolicies (GWT 1.3) is applied and Object must be
IsSerializable.
On Wed, Oct 15, 2008 at 4:54 PM, olivier nouguier
[EMAIL PROTECTED] wrote:
Hi
You should call :
