On Apr 5, 8:47 pm, powwow <jimmy.w...@gmail.com> wrote: > OMG! This one nearly killed our project. When SOP was introduced in > development mode for GWT 2.0 our project screeched to a halt. We have > a huge application with a GWT front end communicating with a Rails > server doing JSON requests. We had GWT running onhttp://127.0.0.1:8888 > and needed to connect to the rails server which ran onhttp://127.0.0.1:3000. > The only difference was the port. Our application HAD to run in IE > (no Firefox or Chome). We had hundreds of JSON calls doing GET, > POST, PUT, DELETE all using RequestBuilder to communicate. > > We tried ProxyServer scripts to forward urls to the Rails server, but > many were just too basic not being able to handle PUTs, DELETEs, form > uploads, headers and everything else. Half the calls worked, and half > the calls failed. We didn't have time to program the perfect > ProxyServer servlet. > > We tried all the hacks including the Eclipse built in proxy server, > enabling cross domain communication in IE in the options, lowering > browser security levels, installing and uninstalling software, etc., > all with no luck. > > But we found something that did work for the time being. Here is a > work around if you need to bypass SOP: Use IE 8! We used IE7 and it > didn't work, but IE8 works!
How about just using the -noserver argument to not run the server (as you don't need it) and the -startUrl argument to pass the Rails app URL so GWT gives you it back with the ?gwt.codesrv=... appended appropriately. See http://code.google.com/webtoolkit/doc/latest/FAQ_DebuggingAndCompiling.html#How_do_I_use_my_own_server_in_hosted_mode_instead_of_GWT's -- 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.
