The problem with 'Object' stuffed into a type you send via RPC is, that you can then use this 'Object' to transfer only types otherwise found and thus known by the RPC registry. You can create a dummy function in your RPC service, give it a parameter class Dummy, and in this class you can enumerate (by a simple field member declaration) all the types of objects you want to be able to carry in the 'Object' reference above. That way the RPC registry will learn about them.
On Jul 25, 7:24 am, ramraj <sriramaraju2...@gmail.com> wrote: > Hi all, > > I am new to this rpc,i facing a problem with Date type,I have one > methods that takes Map<String,Object> > argument,when i am trying to send to Date as value for that map i am > getting exception like > > java.lang.reflect.InvocationTargetException > java.lang.AssertionError: Not enough methods, expecting 3 saw 2 > > If a change to Map<String,Date> it is working fine > > please give suggessions, --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
