Mule API控制台返回状态0，为什么

Question

我正在使用mule开发一个API，这个API使用API控制台使用raml测试应用程序。我的API在Internet Explorer和Postman中运行得很好，但在Chrome或Mozilla中却不是这样。这是我从Mozilla控制台中得到的错误

"Error: [$rootScope:inprog] $apply already in progress
http://errors.angularjs.org/1.3.20/$rootScope/inprog?p0=%24apply
minErr/<@https://127.0.0.1:8444/api/loanmgmt/1.0/console/scripts/api-console-vendor.js:49455:12
beginPhase@https://127.0.0.1:8444/api/loanmgmt/1.0/console/scripts/api-console-vendor.js:64316:15
$RootScopeProvider/this.$get</Scope.prototype.$apply@https://127.0.0.1:8444/api/loanmgmt/1.0/console/scripts/api-console-vendor.js:64060:11
apply@https://127.0.0.1:8444/api/loanmgmt/1.0/console/scripts/api-console.js:1044:11
handleResponse@https://127.0.0.1:8444/api/loanmgmt/1.0/console/scripts/api-console.js:1096:11
RAML.Directives.sidebar/<.controller</$scope.tryIt/</<@https://127.0.0.1:8444/api/loanmgmt/1.0/console/scripts/api-console.js:1426:37
.Deferred/promise.then/</</<@https://127.0.0.1:8444/api/loanmgmt/1.0/console/scripts/api-console-vendor.js:32199:30
jQuery.Callbacks/fire@https://127.0.0.1:8444/api/loanmgmt/1.0/console/scripts/api-console-vendor.js:32042:10
jQuery.Callbacks/self.add@https://127.0.0.1:8444/api/loanmgmt/1.0/console/scripts/api-console-vendor.js:32088:7
.Deferred/promise.then/</<@https://127.0.0.1:8444/api/loanmgmt/1.0/console/scripts/api-console-vendor.js:32198:8
.each@https://127.0.0.1:8444/api/loanmgmt/1.0/console/scripts/api-console-vendor.js:29317:14
.Deferred/promise.then/<@https://127.0.0.1:8444/api/loanmgmt/1.0/console/scripts/api-console-vendor.js:32195:7
.Deferred@https://127.0.0.1:8444/api/loanmgmt/1.0/console/scripts/api-console-vendor.js:32255:4
.Deferred/promise.then@https://127.0.0.1:8444/api/loanmgmt/1.0/console/scripts/api-console-vendor.js:32194:13
RAML.Directives.sidebar/<.controller</$scope.tryIt/<@https://127.0.0.1:8444/api/loanmgmt/1.0/console/scripts/api-console.js:1424:17
Anonymous.prototype.authenticate/<.then@https://127.0.0.1:8444/api/loanmgmt/1.0/console/scripts/api-console.js:2194:33
RAML.Directives.sidebar/<.controller</$scope.tryIt@https://127.0.0.1:8444/api/loanmgmt/1.0/console/scripts/api-console.js:1421:15
$parseFunctionCall@https://127.0.0.1:8444/api/loanmgmt/1.0/console/scripts/api-console-vendor.js:61866:15
ngEventHandler/</callback@https://127.0.0.1:8444/api/loanmgmt/1.0/console/scripts/api-console-vendor.js:71092:17
$RootScopeProvider/this.$get</Scope.prototype.$eval@https://127.0.0.1:8444/api/loanmgmt/1.0/console/scripts/api-console-vendor.js:63962:16
$RootScopeProvider/this.$get</Scope.prototype.$apply@https://127.0.0.1:8444/api/loanmgmt/1.0/console/scripts/api-console-vendor.js:64061:18
ngEventHandler/<@https://127.0.0.1:8444/api/loanmgmt/1.0/console/scripts/api-console-vendor.js:71097:17
jQuery.event.dispatch@https://127.0.0.1:8444/api/loanmgmt/1.0/console/scripts/api-console-vendor.js:33377:15
jQuery.event.add/elemData.handle@https://127.0.0.1:8444/api/loanmgmt/1.0/console/scripts/api-console-vendor.js:33064:6
"

这是api.console.js中生成错误的一行，但我不知道为什么。

jQuery.ajax(request.toOptions()).then(
function(data, textStatus, jqXhr) { handleResponse(jqXhr); },
function(jqXhr) { handleResponse(jqXhr); }
);

Answer 1

由于这是一个Mule应用程序，我不是javascript开发人员，所以我很难通过javascript和浏览器控制台来攻击这个问题，事实上，关于这个问题的信息并不多。这实际上是一个RAML问题，因为它没有发送请求，调试器也从未停止过，所以，我在RAML中进行了一些挖掘，删除了其中的一些部分，有一个参数导致了问题的出现，因为它与api设计不符，如果我早点研究这种方法，我会更快地解决这个问题。