Thanks for the reply. I only had GWT 2.0.2 in my classpath when I got the error (which, incidentally, is caused when a callback throws an exception and the callback's onFailure() method is called. The actual exception thrown is a com.google.gwt.user.client.rpc.IncompatibleRemoteServiceException during a com.google.gwt.user.server.rpc.RPC.decodeRequest).
I am having no problems with GWT 1.7.1 using the same codebase in my project (i.e., my code hasn't changed and I'm confident it is nothing I did in my code to cause the error). Before I dare try GWT 2.0.x again, I need to see some response that this error has been fixed (by the GWT team). - Garry On Feb 19, 3:44 am, Flemming Boller <flemming.bol...@gmail.com> wrote: > I had the same error , but it was because I had a mix of GWT 2 and GWT 1.7 > jarfiles on my running classpath. (also using Intellij) > > Br > Flemming > > On Thu, Feb 18, 2010 at 11:47 PM, gazarcher <garry.arc...@gmail.com> wrote: > > Up until this week I was using IntelliJ IDEA 9.0 with GWT 1.7.1 on Mac > > OS X 10.5 and decided to upgrade to GWT 2.0.2 per the instructions on > > the GWT Website, including installing the GWT plugin into Firefox. > > > After recompiling and running my application with several GWT modules > > and running in Firefox 3.5.7, Firefox 3.6 and Safari 4.0.3, the GWT > > modules all give the same error: > > > Parameter 0 of is of an unknown type 'java.lang.String/2004016611' > > > but even before that GWT spewed "ERROR: Failed to parse the policy > > file <policy file pathname>" for each module. > > > I've cleaned out output folders/directories in IntelliJ, deleted > > caches for IntelliJ and Firefox, and tried again, but with the same > > result. Nothing has changed in my code. > > > I cleared out output folders/directories in IntelliJ, deleted caches > > for IntelliJ and Firefox again and uninstalled GWT 2.0.2 from my > > IntelliJ project, reinstalled GWT 1.7.1, compiled and every thing ran > > fine again. > > > I've looked around the discussion groups and other people appear to be > > having the same problem with GWT 2.0.x.. so even though GWT 2.0 has > > gone through beta, early access, etc., and has now gone up two more > > versions, this is still an issue, and not just for me. I understand > > the GWT version 1.0.7511 plugin for Firefox also has an issue for some > > folks. I don't know if it is this causing the problem. > > > Is anybody actually working with GWT 2.0 in their projects? If so, is > > there a workaround for this issue if they hit the same problem? > > > Is anyone on the GWT team aware of this issue and working on it? > > > At the moment, GWT 2.0.x is unusable for me and trying to use it is > > holding up my work. I'm going back to GWT 1.7.1 until I find a > > solution (or you do!). > > > Any help on this matter is *greatly* appreciated. > > > Cheers, > > - Garry > > > -- > > 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<google-web-toolkit%2bunsubscr...@googlegroups.com> > > . > > For more options, visit this group at > >http://groups.google.com/group/google-web-toolkit?hl=en. -- 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.