Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
How to figure out this problem?
Message
De
10/02/2015 16:05:58
 
 
Information générale
Forum:
Javascript
Catégorie:
Autre
Divers
Thread ID:
01615127
Message ID:
01615128
Vues:
49
This message has been marked as a message which has helped to the initial question of the thread.
Use the developer tools in the browser to see what is actually getting sent.

>Hi everybody,
>
>I'm trying to figure out a complex problem.
>
>We have a directive (written by the colleague) with the following code:
>
>
>  var dialogTypes = [{ name: 'layouts', location: '/api/layouts/getlayouts/' },
>                              { name: 'forms', location: '/api/forms/getforms' }];
>                        var location = '';
>                        for (var i = 0; i < dialogTypes.length; i++) {
>                            if (dialogTypes[i].name == $scope.param) {
>                                location = dialogTypes[i];
>                                break;
>                            }
>                        }
>
>                        $scope.table = searchScreenService.getTable('Descrip', [
>                               { name: 'descrip', displayName: resourceFactory.getResource('Labels', 'descrip') },
>                               { name: 'description', displayName: resourceFactory.getResource('Labels', 'type') }
>                        ]);
>                        $scope.queryRequest = searchScreenService.getQueryRequest();
>
>                        var deferred = $q.defer();
>                        $scope.location = location;
>
>                        $http.get(location.location, { params: $scope.queryRequest })
>                    .success(function (data, status, headers, config) {
>                        deferred.resolve(data);
>                    })
>                    .error(function (data, status, header, config) {
>                        deferred.reject(status);
>                    });
>
>I am testing in IE and I am getting hit on the reject and I see status being 400. The APIController's method is not even getting hit.
>
>I know that this code worked before. I made some changes in the LayoutsAPIController (and adapter and repository classes) to use a new class (LayoutsList) instead of the original Layouts class.
>
>I am wondering how can I figure out what may be the problem here and why now I'm getting the 400 as a return status?
>
>I already tested the Layouts page by itself and everything is working smoothly. It is only not working now from that directive.
>
>Thanks in advance.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform