On 12 August 2014 22:35, <[email protected]> wrote: > > > - Thank you. Still no response: though I checked and made sure no > authorization is required now. > > Could it be a CORS kind of thing? > > I am running the ISIS app on localhost:8080 and angular on localhost:8888 > ... > > Any idea? > > Yep, CORS.
My recommendation would be to have Isis also serve up AngularJS... just put those files under src/main/webapp. If you don't want to do that, then I know it's possible to run Chrome with CORS disabled, see eg [1] Or, you could spend the time enabling CORS. I did start (last Xmas, and then ran out of time) building an AngularJS app myself against Isis, and there's a repo on github. In it there is (somewhat redundantly I now suspect) a CORS filter; you can grab it here [2] Dan [1] http://stackoverflow.com/questions/3102819/disable-same-origin-policy-in-chrome [2] https://github.com/danhaywood/zzz-playtime-isis-todoapp-angularjs/blob/master/webapp/src/main/java/org/eclipse/jetty/servlets/CrossOriginFilter.java
