Version: SmartClient 8.2
Is the transaction queuing broken in 8.2? (nightly build as of 2011-01-10)
If I set "disableQueuing: true" then I get two POST's sent to the server as expected on a multi component drop add operation. But if I let the system attempt to queue the POST request to the server then I get the following sent to the server:
The system recognizes that it is supposed to be sending two operations to the server, but the operation data is missing.
The only change that I make between the working version and the failing version is setting disableQueuing:true/false.
When set to true the POST includes all the necessary data.
When set to false the POST is missing all the necessary data.
I have tried with dataFormat:"xml" and dataFormat:"json" with the same results.
I have also tried dataProtocol:'postParams' and dataProtocol: 'postMessage' with the same result.
I assume there is some other piece that I am missing to get this to work properly. Any pointers on what I'm missing would be greatly appreciated.
Thanks,
Chris
Is the transaction queuing broken in 8.2? (nightly build as of 2011-01-10)
If I set "disableQueuing: true" then I get two POST's sent to the server as expected on a multi component drop add operation. But if I let the system attempt to queue the POST request to the server then I get the following sent to the server:
Code:
{ transaction: { transactionNum: 70, operations: [null, null]}}
The only change that I make between the working version and the failing version is setting disableQueuing:true/false.
When set to true the POST includes all the necessary data.
When set to false the POST is missing all the necessary data.
I have tried with dataFormat:"xml" and dataFormat:"json" with the same results.
I have also tried dataProtocol:'postParams' and dataProtocol: 'postMessage' with the same result.
I assume there is some other piece that I am missing to get this to work properly. Any pointers on what I'm missing would be greatly appreciated.
Thanks,
Chris
Comment