Add gwt-servlet-deps.jar to your project. It comes with gwt sdk distribution.
Cheers, Luca On 15 Mag, 14:42, Joshua Kappon <[email protected]> wrote: > Thank! > > I added the json-20090211.jar to my build path and it solved the > problem! > > On May 14, 10:43 pm, Hilco Wijbenga <[email protected]> wrote: > > > > > > > > > On 13 May 2011 16:26, Joshua Kappon <[email protected]> wrote: > > > > Hi All > > > > I'm trying to upgrade my project to use GWT 2.3 > > > I changed all the imports and xml project and web.xml to point to the > > > new packages locations. > > > > butRequestFactorycalls still don't work. > > > > when running in dev mode I get the following exceptions on run time: > > > > java.lang.NoClassDefFoundError: org/json/JSONException > > > at > > > com.google.web.bindery.autobean.shared.impl.StringQuoter.createSplittable(S > > > tringQuoter.java: > > > 58) > > > at > > > com.google.web.bindery.autobean.shared.impl.AbstractAutoBean.<init>(Abstrac > > > tAutoBean.java: > > > 71) > > > > this originates from: > > > > Caused by: java.lang.ClassNotFoundException: null > > > at com.google.gwt.dev.shell.CompilingClassLoader > > > $MultiParentClassLoader.findClass(CompilingClassLoader.java:365) > > > at java.lang.ClassLoader.loadClass(Unknown Source) > > > > that is caused by a code call to a > > > > request.doSomething() > > > or a > > > request.create(someobject.class) > > > > Did someone else stumble upon something like this? > > > I'm clueless. > > > Yes, I ran into something similar. I fixed the complaint about not > > finding JSONException by > > addinghttp://repo1.maven.org/maven2/org/json/json/20090211/json-20090211.jar > > to my POM. I find it very strange this should be necessary. We're > > supposed to be on the client, in a JavaScript environment after all. > > :-) I have not researched this any further so I don't know whether you > > need that JSON JAR in the WAR as well or if it's just for dev mode. > > > The error reporting in RF is not very helpful, unfortunately. The root > > cause for me just said something like "Server error: null". It turned > > out that the hashCode() methods on two of my DTOs referenced each > > other. That obviously led to an infinite loop and apparently to > > "Server error: null". :-) (I guess that's how the programming gods > > punish people who do not write unit tests. ;-) ) > > > Oh, and don't waste any time on getting GWT/RF's logging to run. It's > > completely useless. I had it set to FINEST but it basically only > > reported "sent something" and "received something". No mention of what > > that something was. Not helpful at all. > > > I suggest you start adding helpful GWT.log (client side) and > > System.out.println (server side) statements and start debugging. It > > took me several hours. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. 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.
