We are encountering a problem where events are not being saved in the database. It appears that some events go to ‘Wait’ state and are pushed into the _in_progress list in the data processor object. The javascript code never fires the Java database code to store the changes, neither does it fire any of the pre event handlers. We need your help in determining why this takes place and how to handle this issue. Our application needs to handle errors gracefully and the user needs to be notified if their event can not be saved. Please see attached image showing the _in_progress ‘Wait’ state.
It possible that previous data saving attempt failed, and instead of valid XML with error type had return some error text or just an empty response. DataProcessor will not allow to update record second time, while valid response for previous operation not received. So empty or non xml response can lock the record in a similar way.
We are seeing this issue if the network is disconnected or the connection has been disturbed. In some cases if the device goes to sleep then wakes up we end up with this scenario. The challenge we are having is that neither Java code nor the JavaScript code gets any notification as to something went wrong. The user continues to work as if everything has been saved yet their changes are lost. How do we detect this condition? Does the DHTMLX Scheduler has a mode that disables this behavior where the calling code is notified when an error takes place rather than going into wait state? If not is there a workaround that we implement.
Yep, I see the problem.
Unfortunately the existing version doesn’t have any special event in case of invalid server side response. We will add an extra handler in the next build.
If you have a support subscription - please open a ticket to receive the updated version ASAP
We plan to release Scheduler 5.0 at September-October 2014. It will have the extra handler for sure. I’m not sure about intermediate builds, so far we don’t have major known bugs, that is why there are no plans for hotfix builds
Get a guaranteed answer from DHTMLX technical support team
under the most suitable support plan
