javascript - Using Restangular with the same URL but different files -


i need communicate rest web service via angular , i'm using restangular i'm running difficulty. have use same url & post 2 different files. i'm setting base url in .config in app.js , service.js i'm setting other url via restangularconfigurer. baseurl in config has query string appended it. second url in service not. want baseurl in config , post factory input. below example of code

app.js

'use strict';  angular .module('testapp', [   'nganimate',   'ngcookies',   'ngresource',   'ngroute',   'ngsanitize',   'ngtouch',   'ui.bootstrap',   'nggrid',   'google-maps',   'ngmessages',   'restangular' ]) .config(function (restangularprovider, $routeprovider) {    restangularprovider.setbaseurl('http://dev.domain.com:9005/question-ws.htm?&areacode=215');    $routeprovider     .when('/', {       templateurl: 'views/main.html',       controller: 'mainctrl'     })  });

service.js

'use strict';  angular.module('testapp')   .factory('nextrestangular', function($http, $sce, restangular){     return restangular.withconfig(function(restangularconfigurer) {       restangularconfigurer.setbaseurl('http://dev.domain.com:9005/next-question-ws.htm');     });   });

controller.js

'use strict';  angular.module('testapp')   .controller('screenctrl', function ($scope, restangular, nextrestangular) {      restangular.all().getlist();      nextrestangular.all().getlist();    });

i can't seem restangular , can't post nextrestangular. file structure able support this? going wrong?

restangular service handle rest api restful resources.

the .htm in urls leads me believe response not json. don't believe restangular work if case. recommend looking ngresource or $http. if response json, following should on way.

in example, baseurl should "http://dev.domain.com:9005".

restangularprovider.setbaseurl('http://dev.domain.com:9005');

i have not used setrequestsuffix before may allow have .htm.

restangularprovider.setrequestsuffix('.htm');

then api calls should this.

restangular.all('next-question-ws').get({areacode: 215}); restangular.all('next-question-ws').post(   // json payload here. });

Comments

Post a Comment

Popular posts from this blog

javascript - RequestAnimationFrame not working when exiting fullscreen switching space on Safari -

request animation frame stops working when exiting fullscreen clicking on original space's safari window. fine if fullscreen mode canceled escape key or calling cancelfullscreen(). steps reproduce: open https://dl.dropboxusercontent.com/u/769042/prezi/safari-fullscreen.html click "draw raf", kittie appears click "fullscreen", go fullscreen click "draw raf", kittie appears go space original safari was, showing "click exit fullscreen mode", click anywhere, out fullscreen click "draw raf", nothing happens what handling click calling: window.requestanimationframe(draw); which draws on canvas context: function draw() { ctx.drawimage(img, math.random()*500|0, math.random()*400|0, 100, 100); } i checked .hidden , .visibilitystate, updated correctly. tested on osx 10.9.3, safari 7.0.4 (9537.76.4). has workaround/solution other switching old settimeout? this sounds webkit bug 88940 : using reque...
Read more

jsf - How to ajax update an item in the footer of a PrimeFaces dataTable? -

this visual of table have: +---------+------------+-------------------+ | header1 | header2 | header3 | +---------+------------+-------------------+ | row | input | calc'ed output | | row b | input b | calc'ed output b | | etc.. | etc.. | etc.. | +---------+------------+-------------------+ | total: total calc'ed output | +------------------------------------------+ and stripped-down code: <p:datatable id="mytable" value="#{mybean.somelist}" var="currentitem"> <p:column headertext="header1"> <h:outputtext value="#{currentitem.name}" /> </p:column> <p:column headertext="header2"> <pe:inputnumber value="#{currentitem.inputval}"> <p:ajax event="change" listener="#{mybean.changelistener}" update="outputval outputtotal...
Read more

django - CSRF verification failed. Request aborted. CSRF cookie not set -

error: reason given failure: csrf cookie not set. in general, can occur when there genuine cross site request forgery, or when django's csrf mechanism has not been used correctly. post forms, need ensure: browser accepting cookies. view function uses requestcontext template, instead of context. in template, there {% csrf_token %} template tag inside each post form targets internal url. if not using csrfviewmiddleware, must use csrf_protect on views use csrf_token template tag, accept post data. you're seeing section of page because have debug = true in django settings file. change false, , initial error message displayed. can customize page using csrf_failure_view setting. did find, nothing helped, must foolish(( my template <form method="post">{% csrf_token %} {% field in form %} <div class="control-group"> {{ field }} </div> {% endfor %} <input type=...
Read more