I'm glad I could help. I took the chance to register to the wiki and update the example, so that this problem should no longer arise.
Regards, Stefan jeffmil schrieb: > Stefan, that fixed it! I was looking at the Manual v0.7 >> Transport-API > (AJAX) document and should have checked the API documentataion. Thanks so > much for your help. qooxdoo is a great framework! > > - Jeff > > > Fa. Linstep, Stefan Volbers wrote: >> Hi Jeff, >> >> please try to alert (e.getContent()); >> instead of e.getData.getContent() >> >> The getData method is deprecated since some time (see >> http://demo.qooxdoo.org/current/apiviewer/#qx.io.remote.Response >> ). >> >> The timeout would also take place if you just missed to answer your >> "completed" event handler's alert by clicking it away in time - I don't >> know why that happens. >> >> HTH >> >> Stefan >> >> >> jeffmil schrieb: >>> Folks, I'm having a problem with Ajax remote access to a normal, fully >>> qualified URL on the same server:port the client is. Here's my code: >>> >>> var req = new qx.io.remote.Request(pURL, "GET", "text/plain"); >>> //req.setMethod("GET"); >>> //req.setTimeout(10000); >>> req.addEventListener("completed", function(e) { >>> alert("Got lyrics for " + pURL + " = " + >>> e.getData.getContent()); >>> document.forms[1].elements[0].value = >>> e.getData.getContent(); >>> }); >>> >>> /* >>> req.addEventListener("timeout", function(e) { >>> alert("Request for lyrics for " + pURL + " timed out!"); >>> document.forms[1].elements[0].value = >>> e.getData.getContent(); >>> }); >>> */ >>> req.send(); >>> >>> I had the timeout event listener in there because that's what happens. >>> The >>> status messages in the separate qooxdoo status display window indicate a >>> timeout. The URL exists and all should be fine with the request. And >>> the >>> request actually does work! In fact, when I run it in Eclipse and run >>> the >>> request/response through the TCP/IP Monitor I can see the response text >>> coming back correctly. It's all there. All is good. Thing is, it just >>> doesn't get returned in the qooxdoo response object, apparently. And the >>> timeout event fires after the default 5 seconds. Even when I set the >>> request timeout to 10,000 millis it times out. Am I missing something >>> about >>> getting the data out of the response? >>> >>> I'm using qooxdoo 0.73 on Windows XP, with Tomcat 6.something. The >>> correct >>> text is there in the HTTP response. It seems it just doesn't make it >>> into >>> the qooxdoo response object -- I don't think. Any ideas about what could >>> be >>> wrong? >>> >>> Thanks very much, >>> >>> Jeff >>> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference >> Don't miss this year's exciting event. There's still time to save $100. >> Use priority code J8TL2D2. >> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone >> _______________________________________________ >> qooxdoo-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel >> >> > ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
