Hello Quu, You obviously control Server B because you load the application from there. Can you also control server A? In that case you could wrap the XML with a couple techniques. The iframe technique for example would wrap the XML into a big javascript string and publish it to your application, i.e. via the window.name transport. You really will have to use some kind of javascript here because that is the only way to comply with the same origin policy: the SOP makes sure that a script can only get information from a different domain if that domain offers the data, i.e. by actively exporting it via javascript. Since XML is a passive document format, it cannot do that.
On Jun 11, 10:02 pm, Quu <[email protected]> wrote: > I want to, inside of my GWT application, load an XML document from a > different server then where the base page is from. My page is on > server A, and the GWT compiled javascript is on a different server, > location B. The XML I am trying to read is at the same location, B, so > why can't the JS loaded from there access ti with out tripping the SOP > error?. > > I used to be able to load XML from a remote site as long as the .html > file hosting the GWT app had a link to an image from the same location > as the XML. This worked in at least 1.7 of GWT, though I suspect it is > more the fact that I have a newer web browser since then. > > I have looked > athttp://code.google.com/webtoolkit/doc/latest/tutorial/Xsite.html > and I don't think I can specifically use any of the tricks there. They > seam to be JSON specific, and require a smart backend to append the > callback to the JSON returned text. -- 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.
