Derrell Lipman wrote:
> There are two issues here. Firstly, you should not reuse the Request object.
> If you create a new request object, you wouldn't (couldn't) see the content
> of a previous request in your new request's response. Request objects are
> intended to be single-use.
>
> The other issue is that the content is not being recorded when the type is
> "failed". See my response in your other message on this topic, and try
> applying the patch I provided. Once you confirm the patch solves your
> problem (assuming you're using a unique Request object for each request) and
> you've created the bug report, I'll apply the fix and close the bug.
>
Thanks for the patch and the tips. I'm using a new request in all
listeners every time. I even tried "delete req;" inside the end of the
event listeners too. But same problem. Also, I applied your patch, but
still got "null".
I tried this:
> var vResponse = qx.event.Registration.createEvent(value,
> qx.io.remote.Response);
> alert("Value is:" + value + " and content is:" +
> vImpl.getResponseContent());
in line 880 of Exchange.js, the alert line being the only line added and
it also showed "failed" state, but an empty "null" content as shown below:
> Value is:failed and content is:null
Firebug shows "Login failed!!!" as the content from rails, which is the
right content of course. So the content isn't even reaching till line 880.
cheers,
skar.
--
--
The life so short, the craft so long to learn.
------------------------------------------------------------------------------
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
