N
Nicoara Radu
Guest
When logging out and discarding a JSDO session and then creating a new one and logging in again, sometimes on the very next request (could be an addCatalog, a fill, etc.), the JSDO will throw an XmlHttpRequest InvalidStateException stating that the request's state must be OPENED. After some debugging I have found that in the following method: progress.data.AuthenticationProvider.prototype._openRequestAndAuthorize, there is a call made to hasClientCredentials() which returns false, even though this is happening after a successful form authentication. Because the hasClientCredentials() method returns false, the xhr.open method is never called and thus when calling xhr.send, the error is thrown. To reproduce this one needs to create a JSDO session, authenticate, add a catalog, create a JSDO and call the fill method at least once, logout, create a new session, authenticate again and attempt creating another JSDO and filling it with data. Is this a bug with the JSDO implementation, or are there API changes in v4.4 that I am not accounting for?
Continue reading...
Continue reading...