This is a migrated thread and some comments may be shown as answers.

stuck in DataSource error handler

10 Answers 1881 Views

Data Source

This is a migrated thread and some comments may be shown as answers.

Roman asked on 10 Oct 2013, 11:46 AM

I'm sure this is pretty simple, but it seems I can't figure it out and I'm also not able to find any example on this.

I'm using a HierarchicalDataSource together with a ListView. Inside the schemas error event, I'd like to navigate to an app-global login page in case the server returns an 401 error. Now it seems I'm stuck in this event, since no matter what I do in there, I can't get to another page. I tried e.preventDefault() (not sure if it makes much sense there) as well as dataSource.cancelChanges() (which will only stop the loading animation).

categories: new kendo.data.HierarchicalDataSource({
            schema: {
                errors: "error"
            },
            error: function(e) {
                if (e.errorThrown == "Unauthorized") {
                    // ...navigate("#login");
                }
            }
})

Thanks for any hints on this.

10 Answers, 1 is accepted

answered on 11 Oct 2013, 11:02 AM

I tried a bit more with his and have to say, that probably the DataSource documentation in either wrong or out of date (or I completely misunderstand something here).

This is from http://docs.kendoui.com/api/framework/datasource#configuration-schema.errors :

schema: {
errors: "error" // twitter's response is { "error": "Invalid query" }
},
error: function(e) {
console.log(e.errors); // displays "Invalid query"
}

I set my server to exactly respond that. There is no way to get the response inside the error callback. Neither trough any of the properties of e nor through "e.errors" (which is undefined). e.status and e.errorThrown both just say "custom error".

answered on 11 Oct 2013, 03:19 PM

Thanks for the hint, but e.xhr is always null. DataSource looks like that:

new kendo.data.DataSource({

                transport: {
                    read: {
                         url: ffkonst.getServiceUrlJsonHttps() + "?p=login"
                        ,type: "POST"
                        ,dataType: "json"
                        ,data: function() {
                            /* build login credentials */
                        }
                    }
                },

                schema: {
                    model: {
                         resultText: "resultText"
                        ,loggedIn: "loggedIn"
                        ,lstring: "l"
                    },
                    errors: "fferror"
                },

                error: function(e) {
                    e.xhr   // --> is null
                }
            })

The server responds with JSON, e.g.:

{"resultText":"invalid nickname","loggedIn":"false","l":false,"fferror":"invalid nickname"}

The error-callback of the DataSource is called, but e.xhr is null.

answered on 14 Feb 2014, 11:53 AM

Well, there it is again. I can't get out of the datasource error handler using application.navigate().

This the relevant code part:

ds = new kendo.data.DataSource({
                    transport: {
                        read: {
                            url: "..."
                            ,type: "POST"
                            ,dataType: "json"
                            ,data: {
                                 ...
                            }
                            ,xhrFields: {
                                withCredentials: true
                            }
                        }
                    },

                    schema: {
                        model: {},
                        errors: "fferror"
                    },

                    error: function(e) {

                        if (e.xhr && e.xhr.status == 401) {
                            e.preventDefault();
                  app.getInstance().navigate("#login");
                  }
                    }
                });

The application does run through navigate(), but nothing happens. As a side note: if I have an alert() directly before navigate(), which delays the processing a bit, navigate() works as expected.