Hi Martin,
Am 20.01.2009 um 14:42 schrieb Martin:
>> Did you try to output the parameters to callAsync before making the
>> call? That would tell you whether the problem is in your application
>> code or in the qooxdoo RPC code. Since there have been no previous
>> reports about such an issue, I guess the problem is somewhere in the
>> app code (and only triggered, for whatever reason, in the build
>> version).
>
> What exactly do you mean by "output the parameters"? I put the
> params as
> param to callAsync, when I call it, I cannot debug the data I think.
> And
> before the call? before the call I just make:
>
> sess = new Object();
> sess["type"]=string;
This is pseudo-code, not your actual source code, right? If so, how do
you actually set the type? Using a string constant (sess["type"] =
"string")? Or using a variable (sess["type"] = string)? Or a method
return value or ... ? I suspect that your problem happens at this
point (and not later on when performing the RPC call).
I suggest you simply put something like
this.debug("Type: " + sess["type"]);
before your RPC call (see http://qooxdoo.org/documentation/0.8/
logging ). Or if you don't want to use the qooxdoo logging system, you
can directly call
console.log("Type: " + sess["type"]);
to make the info appear in the Firebug console.
> sess["value"]=something;
>
> then rpcl.callAsync(function(),"send","method",sess);
>
> I don't know where in my code could the data be modified when its
> just few
> rows above the call :(
I don't think the data is modified (although that's hard to tell
without seeing all the code) - I rather suspect it's wrong to begin
with (see above).
Regards,
Andreas J.
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
